Azure Maps Route Service (preview:1.0)

2025/03/24 • 9 updated methods

Route_PostRouteMatrix (updated)
Description :  > [!NOTE] > > **Azure Maps Route v1 service retirement** > > The Azure Maps [Route v1](/rest/api/maps/route?view=rest-maps-1.0) service is now deprecated and will be retired on 3/31/28. To avoid service disruptions, all calls to Route v1 service will need to be updated to use [Route v2025-01-01](/rest/api/maps/route) service by 3/31/28. For more information, see [Migrate Azure Maps Route 1.0 APIs](/azure/azure-maps/migrate-route-v1-api). The `Post Route Matrix` API is an HTTP `POST` request that allows calculation of a matrix of route summaries for a set of routes defined by origin and destination locations by using an asynchronous (async) request. To make a synchronous (sync) request, see [Post Route Matrix Sync](/rest/api/maps/route/post-route-matrix-sync). For every given origin, the service calculates the cost of routing from that origin to every given destination. The set of origins and the set of destinations can be thought of as the column and row headers of a table and each cell in the table contains the costs of routing from the origin to the destination for that cell. As an example, let's say a food delivery company has 20 drivers and they need to find the closest driver to pick up the delivery from the restaurant. To solve this use case, they can call Matrix Route API. For each route, the travel times and distances are returned. You can use the computed costs to determine which detailed routes to calculate using the Route Directions API. The maximum size of a matrix for async request is **700** and for sync request it's **100** (the number of origins multiplied by the number of destinations). > [!NOTE] > All origins and destinations should be contained in an axis-aligned 400 km x 400 km bounding box. Otherwise some matrix cells will be resolved as OUT_OF_REGION. ### Submit Synchronous Route Matrix Request If your scenario requires synchronous requests and the maximum size of the matrix is less than or equal to 100, you might want to make synchronous request. The maximum size of a matrix for this API is **100** (the number of origins multiplied by the number of destinations). With that constraint in mind, examples of possible matrix dimensions are: 10x10, 6x8, 9x8 (it does not need to be square). ``` POST https://atlas.microsoft.com/route/matrix/sync/json?api-version=1.0&subscription-key={subscription-key} ``` ### Submit Asynchronous Route Matrix Request The Asynchronous API is appropriate for processing big volumes of relatively complex routing requests. When you make a request by using async request, by default the service returns a 202 response code along a redirect URL in the Location field of the response header. This URL should be checked periodically until the response data or error information is available. If `waitForResults` parameter in the request is set to true, user will get a 200 response if the request is finished under 120 seconds. The maximum size of a matrix for this API is **700** (the number of origins multiplied by the number of destinations). With that constraint in mind, examples of possible matrix dimensions are: 50x10, 10x10, 28x25. 10x70 (it does not need to be square). The asynchronous responses are stored for **24** hours. The redirect URL returns a 404 response if used after the expiration period. ``` POST https://atlas.microsoft.com/route/matrix/json?api-version=1.0&subscription-key={subscription-key} ``` Here's a typical sequence of asynchronous operations: 1. Client sends a Route Matrix POST request to Azure Maps 2. The server will respond with one of the following: > HTTP `202 Accepted` - Route Matrix request has been accepted. > HTTP `Error` - There was an error processing your Route Matrix request. This could either be a 400 Bad Request or any other Error status code. 3. If the Matrix Route request was accepted successfully, the Location header in the response contains the URL to download the results of the request. This status URI looks like the following: ``` GET https://atlas.microsoft.com/route/matrix/{matrixId}?api-version=1.0?subscription-key={subscription-key} ``` 4. Client issues a GET request on the download URL obtained in Step 3 to download the results ### Download Sync Results When you make a POST request for Route Matrix Sync API, the service returns 200 response code for successful request and a response array. The response body will contain the data and there will be no possibility to retrieve the results later. ### Download Async Results When a request issues a `202 Accepted` response, the request is being processed using our async pipeline. You will be given a URL to check the progress of your async request in the location header of the response. This status URI looks like the following: ``` GET https://atlas.microsoft.com/route/matrix/{matrixId}?api-version=1.0?subscription-key={subscription-key} ``` The URL provided by the location header will return the following responses when a `GET` request is issued. > HTTP `202 Accepted` - Matrix request was accepted but is still being processed. Please try again in some time. > HTTP `200 OK` - Matrix request successfully processed. The response body contains all of the results.
Reference :  Link ¶

⚶ Changes

{
  "#id": "Route_PostRouteMatrix",
  "Description": {
    "new": "\n\n> [!NOTE]\n>\n> **Azure Maps Route v1 service retirement**\n>\n> The Azure Maps [Route v1](/rest/api/maps/route?view=rest-maps-1.0) service is now deprecated and will be retired on 3/31/28. To avoid service disruptions, all calls to Route v1 service will need to be updated to use [Route v2025-01-01](/rest/api/maps/route) service by 3/31/28. For more information, see [Migrate Azure Maps Route 1.0 APIs](/azure/azure-maps/migrate-route-v1-api).\n\nThe `Post Route Matrix` API is an HTTP `POST` request that allows calculation of a matrix of route summaries for a set of routes defined by origin and destination locations by using an asynchronous (async) request. To make a synchronous (sync) request, see [Post Route Matrix Sync](/rest/api/maps/route/post-route-matrix-sync). For every given origin, the service calculates the cost of routing from that origin to every given destination. The set of origins and the set of destinations can be thought of as the column and row headers of a table and each cell in the table contains the costs of routing from the origin to the destination for that cell. As an example, let's say a food delivery company has 20 drivers and they need to find the closest driver to pick up the delivery from the restaurant. To solve this use case, they can call Matrix Route API.\n\n\nFor each route, the travel times and distances are returned. You can use the computed costs to determine which detailed routes to calculate using the Route Directions API.\n\n\nThe maximum size of a matrix for async request is **700** and for sync request it's **100** (the number of origins multiplied by the number of destinations).\n\n> [!NOTE]\n> All origins and destinations should be contained in an axis-aligned 400 km x 400 km bounding box. Otherwise some matrix cells will be resolved as OUT_OF_REGION.\n\n\n\n### Submit Synchronous Route Matrix Request\nIf your scenario requires synchronous requests and the maximum size of the matrix is less than or equal to 100, you might want to make synchronous request. The maximum size of a matrix for this API is **100** (the number of origins multiplied by the number of destinations). With that constraint in mind, examples of possible matrix dimensions are: 10x10, 6x8, 9x8 (it does not need to be square).\n\n```\nPOST https://atlas.microsoft.com/route/matrix/sync/json?api-version=1.0&subscription-key={subscription-key}\n```\n\n### Submit Asynchronous Route Matrix Request\nThe Asynchronous API is appropriate for processing big volumes of relatively complex routing requests. When you make a request by using async request, by default the service returns a 202 response code along a redirect URL in the Location field of the response header. This URL should be checked periodically until the response data or error information is available. If `waitForResults` parameter in the request is set to true, user will get a 200 response if the request is finished under 120 seconds.\n\n\nThe maximum size of a matrix for this API is **700** (the number of origins multiplied by the number of destinations). With that constraint in mind, examples of possible matrix dimensions are: 50x10, 10x10, 28x25. 10x70 (it does not need to be square).\n\n\nThe asynchronous responses are stored for **24** hours. The redirect URL returns a 404 response if used after the expiration period.\n\n\n\n\n```\nPOST https://atlas.microsoft.com/route/matrix/json?api-version=1.0&subscription-key={subscription-key}\n```\n\nHere's a typical sequence of asynchronous operations:\n1. Client sends a Route Matrix POST request to Azure Maps\n\n2. The server will respond with one of the following:\n\n    > HTTP `202 Accepted` -  Route Matrix request has been accepted.\n\n    > HTTP `Error` - There was an error processing your Route Matrix request. This could either be a 400 Bad Request or any other Error status code.\n\n\n3. If the Matrix Route request was accepted successfully, the Location header in the response contains the URL to download the results of the request. This status URI looks like the following:\n\n  ```\n    GET https://atlas.microsoft.com/route/matrix/{matrixId}?api-version=1.0?subscription-key={subscription-key}\n  ```\n\n\n4. Client issues a GET request on the download URL obtained in Step 3 to download the results\n\n### Download Sync Results\nWhen you make a POST request for Route Matrix Sync API, the service returns 200 response code for successful request and a response array. The response body will contain the data and there will be no possibility to retrieve the results later.\n\n### Download Async Results\nWhen a request issues a `202 Accepted` response, the request is being processed using our async pipeline. You will be given a URL to check the progress of your  async request in the location header of the response. This status URI looks like the following:\n```\n  GET https://atlas.microsoft.com/route/matrix/{matrixId}?api-version=1.0?subscription-key={subscription-key}\n```\n\nThe URL provided by the location header will return the following responses when a `GET` request is issued.\n\n  > HTTP `202 Accepted` - Matrix request was accepted but is still being processed. Please try again in some time.\n\n  > HTTP `200 OK` - Matrix request successfully processed. The response body contains all of the results.",
    "old": "\n\nThe `Post Route Matrix` API is an HTTP `POST` request that allows calculation of a matrix of route summaries for a set of routes defined by origin and destination locations by using an asynchronous (async) request. To make a synchronous (sync) request, see [Post Route Matrix Sync](/rest/api/maps/route/post-route-matrix-sync). For every given origin, the service calculates the cost of routing from that origin to every given destination. The set of origins and the set of destinations can be thought of as the column and row headers of a table and each cell in the table contains the costs of routing from the origin to the destination for that cell. As an example, let's say a food delivery company has 20 drivers and they need to find the closest driver to pick up the delivery from the restaurant. To solve this use case, they can call Matrix Route API.\n\n\nFor each route, the travel times and distances are returned. You can use the computed costs to determine which detailed routes to calculate using the Route Directions API.\n\n\nThe maximum size of a matrix for async request is **700** and for sync request it's **100** (the number of origins multiplied by the number of destinations).\n\n> [!NOTE]\n> All origins and destinations should be contained in an axis-aligned 400 km x 400 km bounding box. Otherwise some matrix cells will be resolved as OUT_OF_REGION.\n\n\n\n### Submit Synchronous Route Matrix Request\nIf your scenario requires synchronous requests and the maximum size of the matrix is less than or equal to 100, you might want to make synchronous request. The maximum size of a matrix for this API is **100** (the number of origins multiplied by the number of destinations). With that constraint in mind, examples of possible matrix dimensions are: 10x10, 6x8, 9x8 (it does not need to be square).\n\n```\nPOST https://atlas.microsoft.com/route/matrix/sync/json?api-version=1.0&subscription-key={subscription-key}\n```\n\n### Submit Asynchronous Route Matrix Request\nThe Asynchronous API is appropriate for processing big volumes of relatively complex routing requests. When you make a request by using async request, by default the service returns a 202 response code along a redirect URL in the Location field of the response header. This URL should be checked periodically until the response data or error information is available. If `waitForResults` parameter in the request is set to true, user will get a 200 response if the request is finished under 120 seconds.\n\n\nThe maximum size of a matrix for this API is **700** (the number of origins multiplied by the number of destinations). With that constraint in mind, examples of possible matrix dimensions are: 50x10, 10x10, 28x25. 10x70 (it does not need to be square).\n\n\nThe asynchronous responses are stored for **24** hours. The redirect URL returns a 404 response if used after the expiration period.\n\n\n\n\n```\nPOST https://atlas.microsoft.com/route/matrix/json?api-version=1.0&subscription-key={subscription-key}\n```\n\nHere's a typical sequence of asynchronous operations:\n1. Client sends a Route Matrix POST request to Azure Maps\n\n2. The server will respond with one of the following:\n\n    > HTTP `202 Accepted` -  Route Matrix request has been accepted.\n\n    > HTTP `Error` - There was an error processing your Route Matrix request. This could either be a 400 Bad Request or any other Error status code.\n\n\n3. If the Matrix Route request was accepted successfully, the Location header in the response contains the URL to download the results of the request. This status URI looks like the following:\n\n  ```\n    GET https://atlas.microsoft.com/route/matrix/{matrixId}?api-version=1.0?subscription-key={subscription-key}\n  ```\n\n\n4. Client issues a GET request on the download URL obtained in Step 3 to download the results\n\n### Download Sync Results\nWhen you make a POST request for Route Matrix Sync API, the service returns 200 response code for successful request and a response array. The response body will contain the data and there will be no possibility to retrieve the results later.\n\n### Download Async Results\nWhen a request issues a `202 Accepted` response, the request is being processed using our async pipeline. You will be given a URL to check the progress of your  async request in the location header of the response. This status URI looks like the following:\n```\n  GET https://atlas.microsoft.com/route/matrix/{matrixId}?api-version=1.0?subscription-key={subscription-key}\n```\n\nThe URL provided by the location header will return the following responses when a `GET` request is issued.\n\n  > HTTP `202 Accepted` - Matrix request was accepted but is still being processed. Please try again in some time.\n\n  > HTTP `200 OK` - Matrix request successfully processed. The response body contains all of the results."
  }
}

⚼ Request

POST:  /route/matrix/{format}
{
x-ms-client-id:
{
Description: Specifies which account is intended for usage in conjunction with the Microsoft Entra ID security model. It represents a unique ID for the Azure Maps account and can be retrieved from the Azure Maps management plane Account API. To use Microsoft Entra ID security in Azure Maps see the following [articles](https://aka.ms/amauthdetails) for guidance. ,
Required: False ,
}
string ,
api-version:
{
Description: Version number of Azure Maps API. ,
Required: True ,
}
string ,
format:
{
Description: Desired format of the response. Only `json` format is supported. ,
Required: True ,
}
string ,
waitForResults:
{
Description: Boolean to indicate whether to execute the request synchronously. If set to true, user will get a 200 response if the request is finished under 120 seconds. Otherwise, user will get a 202 response right away. Please refer to the API description for more details on 202 response. **Supported only for async request**. ,
Required: False ,
}
boolean ,
computeTravelTimeFor:
{
Description: Specifies whether to return additional travel times using different types of traffic information (none, historic, live) as well as the default best-estimate travel time. ,
Required: False ,
}
string ,
sectionType:
{
Description: Specifies which of the section types is reported in the route response.

For example if sectionType = pedestrian the sections which are suited for pedestrians only are returned. Can be specified multiple times in one request, for example, '§ionType=carTrain§ionType=pedestrian§ionType=motorway'. The default sectionType refers to the travelMode input. By default travelMode is set to car ,
Required: False ,
}
array ,
arriveAt:
{
Description: The date and time of arrival at the destination point formatted as a `dateTime` value as defined in [RFC 3339, section 5.6](https://www.rfc-editor.org/rfc/rfc3339#section-5.6), with an optional time zone offset. When a time zone offset is not specified it will be assumed to be that of the destination point. Examples: * 2023-12-19T16:39:57 * 2023-12-19T16:39:57-08:00 The `arriveAt` parameter cannot be used in conjunction with `departAt`, `minDeviationDistance` or `minDeviationTime`. ,
Format: date-time ,
Required: False ,
}
string ,
departAt:
{
Description: The date and time of departure from the origin point formatted as a `dateTime` value as defined in [RFC 3339, section 5.6](https://www.rfc-editor.org/rfc/rfc3339#section-5.6), with an optional time zone offset. When a time zone offset is not specified, it will be assumed to be that of the origin point. * Default value: now * Other value: `dateTime` Examples: * 2023-12-19T16:39:57 * 2023-12-19T16:39:57-08:00 The `departAt` parameter cannot be used in conjunction with `arriveAt`. ,
Format: date-time ,
Required: False ,
}
string ,
vehicleAxleWeight:
{
Description: Weight per axle of the vehicle in kg. A value of 0 means that weight restrictions per axle are not considered. ,
Required: False ,
}
integer ,
vehicleLength:
{
Description: Length of the vehicle in meters. A value of 0 means that length restrictions are not considered. ,
Format: double ,
Required: False ,
}
number ,
vehicleHeight:
{
Description: Height of the vehicle in meters. A value of 0 means that height restrictions are not considered. ,
Format: double ,
Required: False ,
}
number ,
vehicleWidth:
{
Description: Width of the vehicle in meters. A value of 0 means that width restrictions are not considered. ,
Format: double ,
Required: False ,
}
number ,
vehicleMaxSpeed:
{
Description: Maximum speed of the vehicle in km/hour. The max speed in the vehicle profile is used to check whether a vehicle is allowed on motorways. * A value of 0 means that an appropriate value for the vehicle will be determined and applied during route planning. * A non-zero value may be overridden during route planning. For example, the current traffic flow is 60 km/hour. If the vehicle maximum speed is set to 50 km/hour, the routing engine will consider 60 km/hour as this is the current situation. If the maximum speed of the vehicle is provided as 80 km/hour but the current traffic flow is 60 km/hour, then routing engine will again use 60 km/hour. ,
Required: False ,
}
integer ,
vehicleWeight:
{
Description: Weight of the vehicle in kilograms. ,
Required: False ,
}
integer ,
windingness:
{
Description: Level of turns for thrilling route. This parameter can only be used in conjunction with `routeType`=thrilling. ,
Required: False ,
}
string ,
hilliness:
{
Description: Degree of hilliness for thrilling route. This parameter can only be used in conjunction with `routeType`=thrilling. ,
Required: False ,
}
string ,
travelMode:
{
Description: The mode of travel for the requested route. If not defined, default is 'car'. Note that the requested travelMode may not be available for the entire route. Where the requested travelMode is not available for a particular section, the travelMode element of the response for that section will be "other". Note that travel modes bus, motorcycle, taxi and van are BETA functionality. Full restriction data is not available in all areas. ,
Required: False ,
}
string ,
avoid:
{
Description: Specifies something that the route calculation should try to avoid when determining the route. Can be specified multiple times in one request, for example, '&avoid=motorways&avoid=tollRoads&avoid=ferries'. In Route Range requests, the value alreadyUsedRoads must not be used. ,
Required: False ,
}
array ,
traffic:
{
Description: Possible values: * true - Do consider all available traffic information during routing * false - Ignore current traffic data during routing. Note that although the current traffic data is ignored during routing, the effect of historic traffic on effective road speeds is still incorporated. ,
Required: False ,
}
boolean ,
routeType:
{
Description: The type of route requested. ,
Required: False ,
}
string ,
vehicleLoadType:
{
Description: Types of cargo that may be classified as hazardous materials and restricted from some roads. Available vehicleLoadType values are US Hazmat classes 1 through 9, plus generic classifications for use in other countries/regions. Values beginning with USHazmat are for US routing while otherHazmat should be used for all other countries/regions. vehicleLoadType can be specified multiple times. This parameter is currently only considered for travelMode=truck. ,
Required: False ,
}
string ,
routeMatrixQuery:
{
Description: The matrix of origin and destination coordinates to compute the route distance, travel time and other summary for each cell of the matrix based on the input parameters. The minimum and the maximum cell count supported are 1 and **700** for async and **100** for sync respectively. For example, it can be 35 origins and 20 destinations or 25 origins and 25 destinations for async API. ,
Required: True ,
}
{
origins:
{
Description: A valid `GeoJSON MultiPoint` geometry type. Please refer to [RFC 7946](https://tools.ietf.org/html/rfc7946#section-3.1.3) for details. ,
Required: False ,
}
object ,
destinations:
{
Description: A valid `GeoJSON MultiPoint` geometry type. Please refer to [RFC 7946](https://tools.ietf.org/html/rfc7946#section-3.1.3) for details. ,
Required: False ,
}
object ,
}
,
}

⚐ Response (200)

{
formatVersion:
{
Description: Format Version property ,
Required: False ,
}
string ,
matrix:
{
Description: Results as a 2 dimensional array of route summaries. ,
Required: False ,
}
[
{
statusCode:
{
Description: StatusCode property for the current cell in the input matrix. ,
Required: False ,
}
integer ,
response:
{
Description: Response object of the current cell in the input matrix. ,
Required: False ,
}
{
routeSummary:
{
Description: Summary object for route section. ,
Required: False ,
}
{
lengthInMeters:
{
Description: Length In Meters property ,
Required: False ,
}
integer ,
travelTimeInSeconds:
{
Description: Estimated travel time in seconds property that includes the delay due to real-time traffic. Note that even when traffic=false travelTimeInSeconds still includes the delay due to traffic. If DepartAt is in the future, travel time is calculated using time-dependent historic traffic data. ,
Required: False ,
}
integer ,
trafficDelayInSeconds:
{
Description: Estimated delay in seconds caused by the real-time incident(s) according to traffic information. For routes planned with departure time in the future, delays is always 0. To return additional travel times using different types of traffic information, parameter computeTravelTimeFor=all needs to be added. ,
Required: False ,
}
integer ,
departureTime:
{
Description: The estimated departure time for the route or leg. Time is in UTC. ,
Format: date-time ,
Required: False ,
}
string ,
arrivalTime:
{
Description: The estimated arrival time for the route or leg. Time is in UTC. ,
Format: date-time ,
Required: False ,
}
string ,
noTrafficTravelTimeInSeconds:
{
Description: Estimated travel time calculated as if there are no delays on the route due to traffic conditions (e.g. congestion). Included only if computeTravelTimeFor = all is used in the query. ,
Required: False ,
}
integer ,
historicTrafficTravelTimeInSeconds:
{
Description: Estimated travel time calculated using time-dependent historic traffic data. Included only if computeTravelTimeFor = all is used in the query. ,
Required: False ,
}
integer ,
liveTrafficIncidentsTravelTimeInSeconds:
{
Description: Estimated travel time calculated using real-time speed data. Included only if computeTravelTimeFor = all is used in the query. ,
Required: False ,
}
integer ,
fuelConsumptionInLiters:
{
Description: Estimated fuel consumption in liters using the Combustion Consumption Model. Included if vehicleEngineType is set to _combustion_ and constantSpeedConsumptionInLitersPerHundredkm is specified. The value will be non-negative. ,
Format: double ,
Required: False ,
}
number ,
batteryConsumptionInkWh:
{
Description: Estimated electric energy consumption in kilowatt hours (kWh) using the Electric Consumption Model. Included if vehicleEngineType is set to electric and constantSpeedConsumptionInkWhPerHundredkm is specified. The value of batteryConsumptionInkWh includes the recuperated electric energy and can therefore be negative (which indicates gaining energy). If both maxChargeInkWh and currentChargeInkWh are specified, recuperation will be capped to ensure that the battery charge level never exceeds maxChargeInkWh. If neither maxChargeInkWh nor currentChargeInkWh are specified, unconstrained recuperation is assumed in the consumption calculation. ,
Format: double ,
Required: False ,
}
number ,
}
,
}
,
}
,
]
,
summary:
{
Description: Summary object ,
Required: False ,
}
{
successfulRoutes:
{
Description: Number of successful routes in the response. ,
Required: False ,
}
integer ,
totalRoutes:
{
Description: Total number of routes requested. Number of cells in the input matrix. ,
Required: False ,
}
integer ,
}
,
}

⚐ Response (202)

{
location:
{
Description: New URL to check for the results of the long-running operation. ,
}
string ,
}

⚐ Response (default)

{
error:
{
Description: The error object. ,
Required: False ,
}
{
code:
{
Description: The error code. ,
Required: False ,
}
string ,
message:
{
Description: The error message. ,
Required: False ,
}
string ,
target:
{
Description: The error target. ,
Required: False ,
}
string ,
details:
{
Description: The error details. ,
Required: False ,
}
[
{
code:
{
Description: The error code. ,
Required: False ,
}
string ,
message:
{
Description: The error message. ,
Required: False ,
}
string ,
target:
{
Description: The error target. ,
Required: False ,
}
string ,
details:
{
Description: The error details. ,
Required: False ,
}
[
string ,
]
,
additionalInfo:
{
Description: The error additional info. ,
Required: False ,
}
[
{
type:
{
Description: The additional info type. ,
Required: False ,
}
string ,
info:
{
Description: The additional info. ,
Required: False ,
}
object ,
}
,
]
,
}
,
]
,
additionalInfo:
{
Description: The error additional info. ,
Required: False ,
}
[
{
type:
{
Description: The additional info type. ,
Required: False ,
}
string ,
info:
{
Description: The additional info. ,
Required: False ,
}
object ,
}
,
]
,
}
,
}
Route_GetRouteMatrix (updated)
Description :  > [!NOTE] > > **Azure Maps Route v1 service retirement** > > The Azure Maps [Route v1](/rest/api/maps/route?view=rest-maps-1.0) service is now deprecated and will be retired on 3/31/28. To avoid service disruptions, all calls to Route v1 service will need to be updated to use [Route v2025-01-01](/rest/api/maps/route) service by 3/31/28. For more information, see [Migrate Azure Maps Route 1.0 APIs](/azure/azure-maps/migrate-route-v1-api). The `Get Route Matrix` API is an HTTP `GET` request that computes the travel time and distance for all possible pairs in a list of origins and destinations. Unlike the [Get Route Directions](/rest/api/maps/route/get-route-directions) API, which provide detailed route instructions, this API focuses on efficiency by giving you the cost (travel time and distance) of routing from each origin to every destination. For more information, see [Best practices for Azure Maps Route service](/azure/azure-maps/how-to-use-best-practices-for-routing). For every given origin, the service calculates the cost of routing from that origin to every given destination. The set of origins and the set of destinations can be thought of as the column and row headers of a table and each cell in the table contains the costs of routing from the origin to the destination for that cell. As an example, let's say a food delivery company has 20 drivers and they need to find the closest driver to pick up the delivery from the restaurant. To solve this use case, they can call Matrix Route API. For each route, the travel times and distances are returned. You can use the computed costs to determine which detailed routes to calculate using the Route Directions API. The maximum size of a matrix for async request is **700** and for sync request it's **100** (the number of origins multiplied by the number of destinations). ### Submit Synchronous Route Matrix Request If your scenario requires synchronous requests and the maximum size of the matrix is less than or equal to 100, you might want to make synchronous request. The maximum size of a matrix for this API is **100** (the number of origins multiplied by the number of destinations). With that constraint in mind, examples of possible matrix dimensions are: 10x10, 6x8, 9x8 (it does not need to be square). ``` GET https://atlas.microsoft.com/route/matrix/sync/json?api-version=1.0&subscription-key={subscription-key} ``` ### Submit Asynchronous Route Matrix Request The Asynchronous API is appropriate for processing big volumes of relatively complex routing requests. When you make a request by using async request, by default the service returns a 202 response code along a redirect URL in the Location field of the response header. This URL should be checked periodically until the response data or error information is available. If `waitForResults` parameter in the request is set to true, user will get a 200 response if the request is finished under 120 seconds. The maximum size of a matrix for this API is **700** (the number of origins multiplied by the number of destinations). With that constraint in mind, examples of possible matrix dimensions are: 50x10, 10x10, 28x25. 10x70 (it does not need to be square). The asynchronous responses are stored for **24** hours. The redirect URL returns a 404 response if used after the expiration period. ``` GET https://atlas.microsoft.com/route/matrix/json?api-version=1.0&subscription-key={subscription-key} ``` Here's a typical sequence of asynchronous operations: 1. Client sends a Route Matrix GET request to Azure Maps 2. The server will respond with one of the following: > HTTP `202 Accepted` - Route Matrix request has been accepted. > HTTP `Error` - There was an error processing your Route Matrix request. This could either be a 400 Bad Request or any other Error status code. 3. If the Matrix Route request was accepted successfully, the Location header in the response contains the URL to download the results of the request. This status URI looks like the following: ``` GET https://atlas.microsoft.com/route/matrix/{matrixId}?api-version=1.0?subscription-key={subscription-key} ``` 4. Client issues a GET request on the download URL obtained in Step 3 to download the results ### Download Sync Results When you make a GET request for Route Matrix Sync API, the service returns 200 response code for successful request and a response array. The response body will contain the data and there will be no possibility to retrieve the results later. ### Download Async Results When a request issues a `202 Accepted` response, the request is being processed using our async pipeline. You will be given a URL to check the progress of your async request in the location header of the response. This status URI looks like the following: ``` GET https://atlas.microsoft.com/route/matrix/{matrixId}?api-version=1.0?subscription-key={subscription-key} ``` The URL provided by the location header will return the following responses when a `GET` request is issued. > HTTP `202 Accepted` - Matrix request was accepted but is still being processed. Please try again in some time. > HTTP `200 OK` - Matrix request successfully processed. The response body contains all of the results.
Reference :  Link ¶

⚶ Changes

{
  "#id": "Route_GetRouteMatrix",
  "Description": {
    "new": "\n\n> [!NOTE]\n>\n> **Azure Maps Route v1 service retirement**\n>\n> The Azure Maps [Route v1](/rest/api/maps/route?view=rest-maps-1.0) service is now deprecated and will be retired on 3/31/28. To avoid service disruptions, all calls to Route v1 service will need to be updated to use [Route v2025-01-01](/rest/api/maps/route) service by 3/31/28. For more information, see [Migrate Azure Maps Route 1.0 APIs](/azure/azure-maps/migrate-route-v1-api).\n\nThe `Get Route Matrix` API is an HTTP `GET` request that computes the travel time and distance for all possible pairs in a list of origins and destinations. Unlike the [Get Route Directions](/rest/api/maps/route/get-route-directions) API, which provide detailed route instructions, this API focuses on efficiency by giving you the cost (travel time and distance) of routing from each origin to every destination.  For more information, see [Best practices for Azure Maps Route service](/azure/azure-maps/how-to-use-best-practices-for-routing).\n\nFor every given origin, the service calculates the cost of routing from that origin to every given destination. The set of origins and the set of destinations can be thought of as the column and row headers of a table and each cell in the table contains the costs of routing from the origin to the destination for that cell. As an example, let's say a food delivery company has 20 drivers and they need to find the closest driver to pick up the delivery from the restaurant. To solve this use case, they can call Matrix Route API.\n\n\nFor each route, the travel times and distances are returned. You can use the computed costs to determine which detailed routes to calculate using the Route Directions API.\n\n\nThe maximum size of a matrix for async request is **700** and for sync request it's **100** (the number of origins multiplied by the number of destinations).\n\n\n\n### Submit Synchronous Route Matrix Request\nIf your scenario requires synchronous requests and the maximum size of the matrix is less than or equal to 100, you might want to make synchronous request. The maximum size of a matrix for this API is **100** (the number of origins multiplied by the number of destinations). With that constraint in mind, examples of possible matrix dimensions are: 10x10, 6x8, 9x8 (it does not need to be square).\n\n```\nGET https://atlas.microsoft.com/route/matrix/sync/json?api-version=1.0&subscription-key={subscription-key}\n```\n\n### Submit Asynchronous Route Matrix Request\nThe Asynchronous API is appropriate for processing big volumes of relatively complex routing requests. When you make a request by using async request, by default the service returns a 202 response code along a redirect URL in the Location field of the response header. This URL should be checked periodically until the response data or error information is available. If `waitForResults` parameter in the request is set to true, user will get a 200 response if the request is finished under 120 seconds.\n\n\nThe maximum size of a matrix for this API is **700** (the number of origins multiplied by the number of destinations). With that constraint in mind, examples of possible matrix dimensions are: 50x10, 10x10, 28x25. 10x70 (it does not need to be square).\n\n\nThe asynchronous responses are stored for **24** hours. The redirect URL returns a 404 response if used after the expiration period.\n\n\n\n\n```\nGET https://atlas.microsoft.com/route/matrix/json?api-version=1.0&subscription-key={subscription-key}\n```\n\nHere's a typical sequence of asynchronous operations:\n1. Client sends a Route Matrix GET request to Azure Maps\n\n2. The server will respond with one of the following:\n\n    > HTTP `202 Accepted` -  Route Matrix request has been accepted.\n\n    > HTTP `Error` - There was an error processing your Route Matrix request. This could either be a 400 Bad Request or any other Error status code.\n\n\n3. If the Matrix Route request was accepted successfully, the Location header in the response contains the URL to download the results of the request. This status URI looks like the following:\n\n  ```\n    GET https://atlas.microsoft.com/route/matrix/{matrixId}?api-version=1.0?subscription-key={subscription-key}\n  ```\n\n\n4. Client issues a GET request on the download URL obtained in Step 3 to download the results\n\n### Download Sync Results\nWhen you make a GET request for Route Matrix Sync API, the service returns 200 response code for successful request and a response array. The response body will contain the data and there will be no possibility to retrieve the results later.\n\n### Download Async Results\nWhen a request issues a `202 Accepted` response, the request is being processed using our async pipeline. You will be given a URL to check the progress of your  async request in the location header of the response. This status URI looks like the following:\n```\n  GET https://atlas.microsoft.com/route/matrix/{matrixId}?api-version=1.0?subscription-key={subscription-key}\n```\n\nThe URL provided by the location header will return the following responses when a `GET` request is issued.\n\n  > HTTP `202 Accepted` - Matrix request was accepted but is still being processed. Please try again in some time.\n\n  > HTTP `200 OK` - Matrix request successfully processed. The response body contains all of the results.",
    "old": "\n\nThe `Get Route Matrix` API is an HTTP `GET` request that computes the travel time and distance for all possible pairs in a list of origins and destinations. Unlike the [Get Route Directions](/rest/api/maps/route/get-route-directions) API, which provide detailed route instructions, this API focuses on efficiency by giving you the cost (travel time and distance) of routing from each origin to every destination.  For more information, see [Best practices for Azure Maps Route service](/azure/azure-maps/how-to-use-best-practices-for-routing).\n\nFor every given origin, the service calculates the cost of routing from that origin to every given destination. The set of origins and the set of destinations can be thought of as the column and row headers of a table and each cell in the table contains the costs of routing from the origin to the destination for that cell. As an example, let's say a food delivery company has 20 drivers and they need to find the closest driver to pick up the delivery from the restaurant. To solve this use case, they can call Matrix Route API.\n\n\nFor each route, the travel times and distances are returned. You can use the computed costs to determine which detailed routes to calculate using the Route Directions API.\n\n\nThe maximum size of a matrix for async request is **700** and for sync request it's **100** (the number of origins multiplied by the number of destinations).\n\n\n\n### Submit Synchronous Route Matrix Request\nIf your scenario requires synchronous requests and the maximum size of the matrix is less than or equal to 100, you might want to make synchronous request. The maximum size of a matrix for this API is **100** (the number of origins multiplied by the number of destinations). With that constraint in mind, examples of possible matrix dimensions are: 10x10, 6x8, 9x8 (it does not need to be square).\n\n```\nGET https://atlas.microsoft.com/route/matrix/sync/json?api-version=1.0&subscription-key={subscription-key}\n```\n\n### Submit Asynchronous Route Matrix Request\nThe Asynchronous API is appropriate for processing big volumes of relatively complex routing requests. When you make a request by using async request, by default the service returns a 202 response code along a redirect URL in the Location field of the response header. This URL should be checked periodically until the response data or error information is available. If `waitForResults` parameter in the request is set to true, user will get a 200 response if the request is finished under 120 seconds.\n\n\nThe maximum size of a matrix for this API is **700** (the number of origins multiplied by the number of destinations). With that constraint in mind, examples of possible matrix dimensions are: 50x10, 10x10, 28x25. 10x70 (it does not need to be square).\n\n\nThe asynchronous responses are stored for **24** hours. The redirect URL returns a 404 response if used after the expiration period.\n\n\n\n\n```\nGET https://atlas.microsoft.com/route/matrix/json?api-version=1.0&subscription-key={subscription-key}\n```\n\nHere's a typical sequence of asynchronous operations:\n1. Client sends a Route Matrix GET request to Azure Maps\n\n2. The server will respond with one of the following:\n\n    > HTTP `202 Accepted` -  Route Matrix request has been accepted.\n\n    > HTTP `Error` - There was an error processing your Route Matrix request. This could either be a 400 Bad Request or any other Error status code.\n\n\n3. If the Matrix Route request was accepted successfully, the Location header in the response contains the URL to download the results of the request. This status URI looks like the following:\n\n  ```\n    GET https://atlas.microsoft.com/route/matrix/{matrixId}?api-version=1.0?subscription-key={subscription-key}\n  ```\n\n\n4. Client issues a GET request on the download URL obtained in Step 3 to download the results\n\n### Download Sync Results\nWhen you make a GET request for Route Matrix Sync API, the service returns 200 response code for successful request and a response array. The response body will contain the data and there will be no possibility to retrieve the results later.\n\n### Download Async Results\nWhen a request issues a `202 Accepted` response, the request is being processed using our async pipeline. You will be given a URL to check the progress of your  async request in the location header of the response. This status URI looks like the following:\n```\n  GET https://atlas.microsoft.com/route/matrix/{matrixId}?api-version=1.0?subscription-key={subscription-key}\n```\n\nThe URL provided by the location header will return the following responses when a `GET` request is issued.\n\n  > HTTP `202 Accepted` - Matrix request was accepted but is still being processed. Please try again in some time.\n\n  > HTTP `200 OK` - Matrix request successfully processed. The response body contains all of the results."
  }
}

⚼ Request

GET:  /route/matrix/{format}
{
x-ms-client-id:
{
Description: Specifies which account is intended for usage in conjunction with the Microsoft Entra ID security model. It represents a unique ID for the Azure Maps account and can be retrieved from the Azure Maps management plane Account API. To use Microsoft Entra ID security in Azure Maps see the following [articles](https://aka.ms/amauthdetails) for guidance. ,
Required: False ,
}
string ,
api-version:
{
Description: Version number of Azure Maps API. ,
Required: True ,
}
string ,
format:
{
Description: Matrix id received after the Matrix Route request was accepted successfully. ,
Required: True ,
}
string ,
}

⚐ Response (200)

{
formatVersion:
{
Description: Format Version property ,
Required: False ,
}
string ,
matrix:
{
Description: Results as a 2 dimensional array of route summaries. ,
Required: False ,
}
[
{
statusCode:
{
Description: StatusCode property for the current cell in the input matrix. ,
Required: False ,
}
integer ,
response:
{
Description: Response object of the current cell in the input matrix. ,
Required: False ,
}
{
routeSummary:
{
Description: Summary object for route section. ,
Required: False ,
}
{
lengthInMeters:
{
Description: Length In Meters property ,
Required: False ,
}
integer ,
travelTimeInSeconds:
{
Description: Estimated travel time in seconds property that includes the delay due to real-time traffic. Note that even when traffic=false travelTimeInSeconds still includes the delay due to traffic. If DepartAt is in the future, travel time is calculated using time-dependent historic traffic data. ,
Required: False ,
}
integer ,
trafficDelayInSeconds:
{
Description: Estimated delay in seconds caused by the real-time incident(s) according to traffic information. For routes planned with departure time in the future, delays is always 0. To return additional travel times using different types of traffic information, parameter computeTravelTimeFor=all needs to be added. ,
Required: False ,
}
integer ,
departureTime:
{
Description: The estimated departure time for the route or leg. Time is in UTC. ,
Format: date-time ,
Required: False ,
}
string ,
arrivalTime:
{
Description: The estimated arrival time for the route or leg. Time is in UTC. ,
Format: date-time ,
Required: False ,
}
string ,
noTrafficTravelTimeInSeconds:
{
Description: Estimated travel time calculated as if there are no delays on the route due to traffic conditions (e.g. congestion). Included only if computeTravelTimeFor = all is used in the query. ,
Required: False ,
}
integer ,
historicTrafficTravelTimeInSeconds:
{
Description: Estimated travel time calculated using time-dependent historic traffic data. Included only if computeTravelTimeFor = all is used in the query. ,
Required: False ,
}
integer ,
liveTrafficIncidentsTravelTimeInSeconds:
{
Description: Estimated travel time calculated using real-time speed data. Included only if computeTravelTimeFor = all is used in the query. ,
Required: False ,
}
integer ,
fuelConsumptionInLiters:
{
Description: Estimated fuel consumption in liters using the Combustion Consumption Model. Included if vehicleEngineType is set to _combustion_ and constantSpeedConsumptionInLitersPerHundredkm is specified. The value will be non-negative. ,
Format: double ,
Required: False ,
}
number ,
batteryConsumptionInkWh:
{
Description: Estimated electric energy consumption in kilowatt hours (kWh) using the Electric Consumption Model. Included if vehicleEngineType is set to electric and constantSpeedConsumptionInkWhPerHundredkm is specified. The value of batteryConsumptionInkWh includes the recuperated electric energy and can therefore be negative (which indicates gaining energy). If both maxChargeInkWh and currentChargeInkWh are specified, recuperation will be capped to ensure that the battery charge level never exceeds maxChargeInkWh. If neither maxChargeInkWh nor currentChargeInkWh are specified, unconstrained recuperation is assumed in the consumption calculation. ,
Format: double ,
Required: False ,
}
number ,
}
,
}
,
}
,
]
,
summary:
{
Description: Summary object ,
Required: False ,
}
{
successfulRoutes:
{
Description: Number of successful routes in the response. ,
Required: False ,
}
integer ,
totalRoutes:
{
Description: Total number of routes requested. Number of cells in the input matrix. ,
Required: False ,
}
integer ,
}
,
}

⚐ Response (202)

{
location:
{
Description: New URL to check for the results of the long-running operation. ,
}
string ,
}

⚐ Response (default)

{
error:
{
Description: The error object. ,
Required: False ,
}
{
code:
{
Description: The error code. ,
Required: False ,
}
string ,
message:
{
Description: The error message. ,
Required: False ,
}
string ,
target:
{
Description: The error target. ,
Required: False ,
}
string ,
details:
{
Description: The error details. ,
Required: False ,
}
[
{
code:
{
Description: The error code. ,
Required: False ,
}
string ,
message:
{
Description: The error message. ,
Required: False ,
}
string ,
target:
{
Description: The error target. ,
Required: False ,
}
string ,
details:
{
Description: The error details. ,
Required: False ,
}
[
string ,
]
,
additionalInfo:
{
Description: The error additional info. ,
Required: False ,
}
[
{
type:
{
Description: The additional info type. ,
Required: False ,
}
string ,
info:
{
Description: The additional info. ,
Required: False ,
}
object ,
}
,
]
,
}
,
]
,
additionalInfo:
{
Description: The error additional info. ,
Required: False ,
}
[
{
type:
{
Description: The additional info type. ,
Required: False ,
}
string ,
info:
{
Description: The additional info. ,
Required: False ,
}
object ,
}
,
]
,
}
,
}
Route_PostRouteMatrixSync (updated)
Description :  > [!NOTE] > > **Azure Maps Route v1 service retirement** > > The Azure Maps [Route v1](/rest/api/maps/route?view=rest-maps-1.0) service is now deprecated and will be retired on 3/31/28. To avoid service disruptions, all calls to Route v1 service will need to be updated to use [Route v2025-01-01](/rest/api/maps/route) service by 3/31/28. For more information, see [Migrate Azure Maps Route 1.0 APIs](/azure/azure-maps/migrate-route-v1-api). The `Post Route Matrix Sync` API is an HTTP `POST` request that allows calculation of a matrix of route summaries for a set of routes defined by origin and destination locations by using a single synchronous (sync) request. To make an asynchronous (async) request, see [Post Route Matrix](/rest/api/maps/route/post-route-matrix). For every given origin, the service calculates the cost of routing from that origin to every given destination. The set of origins and the set of destinations can be thought of as the column and row headers of a table and each cell in the table contains the costs of routing from the origin to the destination for that cell. As an example, let's say a food delivery company has 20 drivers and they need to find the closest driver to pick up the delivery from the restaurant. To solve this use case, they can call Matrix Route API. For each route, the travel times and distances are returned. You can use the computed costs to determine which detailed routes to calculate using the Route Directions API. The maximum size of a matrix for async request is **700** and for sync request it's **100** (the number of origins multiplied by the number of destinations). ### Submit Synchronous Route Matrix Request If your scenario requires synchronous requests and the maximum size of the matrix is less than or equal to 100, you might want to make synchronous request. The maximum size of a matrix for this API is **100** (the number of origins multiplied by the number of destinations). With that constraint in mind, examples of possible matrix dimensions are: 10x10, 6x8, 9x8 (it does not need to be square). ``` POST https://atlas.microsoft.com/route/matrix/sync/json?api-version=1.0&subscription-key={subscription-key} ``` ### Submit Asynchronous Route Matrix Request The Asynchronous API is appropriate for processing big volumes of relatively complex routing requests. When you make a request by using async request, by default the service returns a 202 response code along a redirect URL in the Location field of the response header. This URL should be checked periodically until the response data or error information is available. If `waitForResults` parameter in the request is set to true, user will get a 200 response if the request is finished under 120 seconds. The maximum size of a matrix for this API is **700** (the number of origins multiplied by the number of destinations). With that constraint in mind, examples of possible matrix dimensions are: 50x10, 10x10, 28x25. 10x70 (it does not need to be square). The asynchronous responses are stored for **24** hours. The redirect URL returns a 404 response if used after the expiration period. ``` POST https://atlas.microsoft.com/route/matrix/json?api-version=1.0&subscription-key={subscription-key} ``` Here's a typical sequence of asynchronous operations: 1. Client sends a Route Matrix POST request to Azure Maps 2. The server will respond with one of the following: > HTTP `202 Accepted` - Route Matrix request has been accepted. > HTTP `Error` - There was an error processing your Route Matrix request. This could either be a 400 Bad Request or any other Error status code. 3. If the Matrix Route request was accepted successfully, the Location header in the response contains the URL to download the results of the request. This status URI looks like the following: ``` GET https://atlas.microsoft.com/route/matrix/{matrixId}?api-version=1.0?subscription-key={subscription-key} ``` 4. Client issues a GET request on the download URL obtained in Step 3 to download the results ### Download Sync Results When you make a POST request for Route Matrix Sync API, the service returns 200 response code for successful request and a response array. The response body will contain the data and there will be no possibility to retrieve the results later. ### Download Async Results When a request issues a `202 Accepted` response, the request is being processed using our async pipeline. You will be given a URL to check the progress of your async request in the location header of the response. This status URI looks like the following: ``` GET https://atlas.microsoft.com/route/matrix/{matrixId}?api-version=1.0?subscription-key={subscription-key} ``` The URL provided by the location header will return the following responses when a `GET` request is issued. > HTTP `202 Accepted` - Matrix request was accepted but is still being processed. Please try again in some time. > HTTP `200 OK` - Matrix request successfully processed. The response body contains all of the results.
Reference :  Link ¶

⚶ Changes

{
  "#id": "Route_PostRouteMatrixSync",
  "Description": {
    "new": "\n\n> [!NOTE]\n>\n> **Azure Maps Route v1 service retirement**\n>\n> The Azure Maps [Route v1](/rest/api/maps/route?view=rest-maps-1.0) service is now deprecated and will be retired on 3/31/28. To avoid service disruptions, all calls to Route v1 service will need to be updated to use [Route v2025-01-01](/rest/api/maps/route) service by 3/31/28. For more information, see [Migrate Azure Maps Route 1.0 APIs](/azure/azure-maps/migrate-route-v1-api).\n\nThe `Post Route Matrix Sync` API is an HTTP `POST` request that allows calculation of a matrix of route summaries for a set of routes defined by origin and destination locations by using a single synchronous (sync) request. To make an asynchronous (async) request, see [Post Route Matrix](/rest/api/maps/route/post-route-matrix). For every given origin, the service calculates the cost of routing from that origin to every given destination. The set of origins and the set of destinations can be thought of as the column and row headers of a table and each cell in the table contains the costs of routing from the origin to the destination for that cell. As an example, let's say a food delivery company has 20 drivers and they need to find the closest driver to pick up the delivery from the restaurant. To solve this use case, they can call Matrix Route API.\n\n\nFor each route, the travel times and distances are returned. You can use the computed costs to determine which detailed routes to calculate using the Route Directions API.\n\n\nThe maximum size of a matrix for async request is **700** and for sync request it's **100** (the number of origins multiplied by the number of destinations).\n\n\n\n### Submit Synchronous Route Matrix Request\nIf your scenario requires synchronous requests and the maximum size of the matrix is less than or equal to 100, you might want to make synchronous request. The maximum size of a matrix for this API is **100** (the number of origins multiplied by the number of destinations). With that constraint in mind, examples of possible matrix dimensions are: 10x10, 6x8, 9x8 (it does not need to be square).\n\n```\nPOST https://atlas.microsoft.com/route/matrix/sync/json?api-version=1.0&subscription-key={subscription-key}\n```\n\n### Submit Asynchronous Route Matrix Request\nThe Asynchronous API is appropriate for processing big volumes of relatively complex routing requests. When you make a request by using async request, by default the service returns a 202 response code along a redirect URL in the Location field of the response header. This URL should be checked periodically until the response data or error information is available. If `waitForResults` parameter in the request is set to true, user will get a 200 response if the request is finished under 120 seconds.\n\n\nThe maximum size of a matrix for this API is **700** (the number of origins multiplied by the number of destinations). With that constraint in mind, examples of possible matrix dimensions are: 50x10, 10x10, 28x25. 10x70 (it does not need to be square).\n\n\nThe asynchronous responses are stored for **24** hours. The redirect URL returns a 404 response if used after the expiration period.\n\n\n\n\n```\nPOST https://atlas.microsoft.com/route/matrix/json?api-version=1.0&subscription-key={subscription-key}\n```\n\nHere's a typical sequence of asynchronous operations:\n1. Client sends a Route Matrix POST request to Azure Maps\n\n2. The server will respond with one of the following:\n\n    > HTTP `202 Accepted` -  Route Matrix request has been accepted.\n\n    > HTTP `Error` - There was an error processing your Route Matrix request. This could either be a 400 Bad Request or any other Error status code.\n\n\n3. If the Matrix Route request was accepted successfully, the Location header in the response contains the URL to download the results of the request. This status URI looks like the following:\n\n  ```\n    GET https://atlas.microsoft.com/route/matrix/{matrixId}?api-version=1.0?subscription-key={subscription-key}\n  ```\n\n\n4. Client issues a GET request on the download URL obtained in Step 3 to download the results\n\n### Download Sync Results\nWhen you make a POST request for Route Matrix Sync API, the service returns 200 response code for successful request and a response array. The response body will contain the data and there will be no possibility to retrieve the results later.\n\n### Download Async Results\nWhen a request issues a `202 Accepted` response, the request is being processed using our async pipeline. You will be given a URL to check the progress of your  async request in the location header of the response. This status URI looks like the following:\n```\n  GET https://atlas.microsoft.com/route/matrix/{matrixId}?api-version=1.0?subscription-key={subscription-key}\n```\n\nThe URL provided by the location header will return the following responses when a `GET` request is issued.\n\n  > HTTP `202 Accepted` - Matrix request was accepted but is still being processed. Please try again in some time.\n\n  > HTTP `200 OK` - Matrix request successfully processed. The response body contains all of the results.",
    "old": "\n\nThe `Post Route Matrix Sync` API is an HTTP `POST` request that allows calculation of a matrix of route summaries for a set of routes defined by origin and destination locations by using a single synchronous (sync) request. To make an asynchronous (async) request, see [Post Route Matrix](/rest/api/maps/route/post-route-matrix). For every given origin, the service calculates the cost of routing from that origin to every given destination. The set of origins and the set of destinations can be thought of as the column and row headers of a table and each cell in the table contains the costs of routing from the origin to the destination for that cell. As an example, let's say a food delivery company has 20 drivers and they need to find the closest driver to pick up the delivery from the restaurant. To solve this use case, they can call Matrix Route API.\n\n\nFor each route, the travel times and distances are returned. You can use the computed costs to determine which detailed routes to calculate using the Route Directions API.\n\n\nThe maximum size of a matrix for async request is **700** and for sync request it's **100** (the number of origins multiplied by the number of destinations).\n\n\n\n### Submit Synchronous Route Matrix Request\nIf your scenario requires synchronous requests and the maximum size of the matrix is less than or equal to 100, you might want to make synchronous request. The maximum size of a matrix for this API is **100** (the number of origins multiplied by the number of destinations). With that constraint in mind, examples of possible matrix dimensions are: 10x10, 6x8, 9x8 (it does not need to be square).\n\n```\nPOST https://atlas.microsoft.com/route/matrix/sync/json?api-version=1.0&subscription-key={subscription-key}\n```\n\n### Submit Asynchronous Route Matrix Request\nThe Asynchronous API is appropriate for processing big volumes of relatively complex routing requests. When you make a request by using async request, by default the service returns a 202 response code along a redirect URL in the Location field of the response header. This URL should be checked periodically until the response data or error information is available. If `waitForResults` parameter in the request is set to true, user will get a 200 response if the request is finished under 120 seconds.\n\n\nThe maximum size of a matrix for this API is **700** (the number of origins multiplied by the number of destinations). With that constraint in mind, examples of possible matrix dimensions are: 50x10, 10x10, 28x25. 10x70 (it does not need to be square).\n\n\nThe asynchronous responses are stored for **24** hours. The redirect URL returns a 404 response if used after the expiration period.\n\n\n\n\n```\nPOST https://atlas.microsoft.com/route/matrix/json?api-version=1.0&subscription-key={subscription-key}\n```\n\nHere's a typical sequence of asynchronous operations:\n1. Client sends a Route Matrix POST request to Azure Maps\n\n2. The server will respond with one of the following:\n\n    > HTTP `202 Accepted` -  Route Matrix request has been accepted.\n\n    > HTTP `Error` - There was an error processing your Route Matrix request. This could either be a 400 Bad Request or any other Error status code.\n\n\n3. If the Matrix Route request was accepted successfully, the Location header in the response contains the URL to download the results of the request. This status URI looks like the following:\n\n  ```\n    GET https://atlas.microsoft.com/route/matrix/{matrixId}?api-version=1.0?subscription-key={subscription-key}\n  ```\n\n\n4. Client issues a GET request on the download URL obtained in Step 3 to download the results\n\n### Download Sync Results\nWhen you make a POST request for Route Matrix Sync API, the service returns 200 response code for successful request and a response array. The response body will contain the data and there will be no possibility to retrieve the results later.\n\n### Download Async Results\nWhen a request issues a `202 Accepted` response, the request is being processed using our async pipeline. You will be given a URL to check the progress of your  async request in the location header of the response. This status URI looks like the following:\n```\n  GET https://atlas.microsoft.com/route/matrix/{matrixId}?api-version=1.0?subscription-key={subscription-key}\n```\n\nThe URL provided by the location header will return the following responses when a `GET` request is issued.\n\n  > HTTP `202 Accepted` - Matrix request was accepted but is still being processed. Please try again in some time.\n\n  > HTTP `200 OK` - Matrix request successfully processed. The response body contains all of the results."
  }
}

⚼ Request

POST:  /route/matrix/sync/{format}
{
x-ms-client-id:
{
Description: Specifies which account is intended for usage in conjunction with the Microsoft Entra ID security model. It represents a unique ID for the Azure Maps account and can be retrieved from the Azure Maps management plane Account API. To use Microsoft Entra ID security in Azure Maps see the following [articles](https://aka.ms/amauthdetails) for guidance. ,
Required: False ,
}
string ,
api-version:
{
Description: Version number of Azure Maps API. ,
Required: True ,
}
string ,
format:
{
Description: Desired format of the response. Only `json` format is supported. ,
Required: True ,
}
string ,
waitForResults:
{
Description: Boolean to indicate whether to execute the request synchronously. If set to true, user will get a 200 response if the request is finished under 120 seconds. Otherwise, user will get a 202 response right away. Please refer to the API description for more details on 202 response. **Supported only for async request**. ,
Required: False ,
}
boolean ,
computeTravelTimeFor:
{
Description: Specifies whether to return additional travel times using different types of traffic information (none, historic, live) as well as the default best-estimate travel time. ,
Required: False ,
}
string ,
sectionType:
{
Description: Specifies which of the section types is reported in the route response.

For example if sectionType = pedestrian the sections which are suited for pedestrians only are returned. Can be specified multiple times in one request, for example, '§ionType=carTrain§ionType=pedestrian§ionType=motorway'. The default sectionType refers to the travelMode input. By default travelMode is set to car ,
Required: False ,
}
array ,
arriveAt:
{
Description: The date and time of arrival at the destination point formatted as a `dateTime` value as defined in [RFC 3339, section 5.6](https://www.rfc-editor.org/rfc/rfc3339#section-5.6), with an optional time zone offset. When a time zone offset is not specified it will be assumed to be that of the destination point. Examples: * 2023-12-19T16:39:57 * 2023-12-19T16:39:57-08:00 The `arriveAt` parameter cannot be used in conjunction with `departAt`, `minDeviationDistance` or `minDeviationTime`. ,
Format: date-time ,
Required: False ,
}
string ,
departAt:
{
Description: The date and time of departure from the origin point formatted as a `dateTime` value as defined in [RFC 3339, section 5.6](https://www.rfc-editor.org/rfc/rfc3339#section-5.6), with an optional time zone offset. When a time zone offset is not specified, it will be assumed to be that of the origin point. * Default value: now * Other value: `dateTime` Examples: * 2023-12-19T16:39:57 * 2023-12-19T16:39:57-08:00 The `departAt` parameter cannot be used in conjunction with `arriveAt`. ,
Format: date-time ,
Required: False ,
}
string ,
vehicleAxleWeight:
{
Description: Weight per axle of the vehicle in kg. A value of 0 means that weight restrictions per axle are not considered. ,
Required: False ,
}
integer ,
vehicleLength:
{
Description: Length of the vehicle in meters. A value of 0 means that length restrictions are not considered. ,
Format: double ,
Required: False ,
}
number ,
vehicleHeight:
{
Description: Height of the vehicle in meters. A value of 0 means that height restrictions are not considered. ,
Format: double ,
Required: False ,
}
number ,
vehicleWidth:
{
Description: Width of the vehicle in meters. A value of 0 means that width restrictions are not considered. ,
Format: double ,
Required: False ,
}
number ,
vehicleMaxSpeed:
{
Description: Maximum speed of the vehicle in km/hour. The max speed in the vehicle profile is used to check whether a vehicle is allowed on motorways. * A value of 0 means that an appropriate value for the vehicle will be determined and applied during route planning. * A non-zero value may be overridden during route planning. For example, the current traffic flow is 60 km/hour. If the vehicle maximum speed is set to 50 km/hour, the routing engine will consider 60 km/hour as this is the current situation. If the maximum speed of the vehicle is provided as 80 km/hour but the current traffic flow is 60 km/hour, then routing engine will again use 60 km/hour. ,
Required: False ,
}
integer ,
vehicleWeight:
{
Description: Weight of the vehicle in kilograms. ,
Required: False ,
}
integer ,
windingness:
{
Description: Level of turns for thrilling route. This parameter can only be used in conjunction with `routeType`=thrilling. ,
Required: False ,
}
string ,
hilliness:
{
Description: Degree of hilliness for thrilling route. This parameter can only be used in conjunction with `routeType`=thrilling. ,
Required: False ,
}
string ,
travelMode:
{
Description: The mode of travel for the requested route. If not defined, default is 'car'. Note that the requested travelMode may not be available for the entire route. Where the requested travelMode is not available for a particular section, the travelMode element of the response for that section will be "other". Note that travel modes bus, motorcycle, taxi and van are BETA functionality. Full restriction data is not available in all areas. ,
Required: False ,
}
string ,
avoid:
{
Description: Specifies something that the route calculation should try to avoid when determining the route. Can be specified multiple times in one request, for example, '&avoid=motorways&avoid=tollRoads&avoid=ferries'. In Route Range requests, the value alreadyUsedRoads must not be used. ,
Required: False ,
}
array ,
traffic:
{
Description: Possible values: * true - Do consider all available traffic information during routing * false - Ignore current traffic data during routing. Note that although the current traffic data is ignored during routing, the effect of historic traffic on effective road speeds is still incorporated. ,
Required: False ,
}
boolean ,
routeType:
{
Description: The type of route requested. ,
Required: False ,
}
string ,
vehicleLoadType:
{
Description: Types of cargo that may be classified as hazardous materials and restricted from some roads. Available vehicleLoadType values are US Hazmat classes 1 through 9, plus generic classifications for use in other countries/regions. Values beginning with USHazmat are for US routing while otherHazmat should be used for all other countries/regions. vehicleLoadType can be specified multiple times. This parameter is currently only considered for travelMode=truck. ,
Required: False ,
}
string ,
routeMatrixQuery:
{
Description: The matrix of origin and destination coordinates to compute the route distance, travel time and other summary for each cell of the matrix based on the input parameters. The minimum and the maximum cell count supported are 1 and **700** for async and **100** for sync respectively. For example, it can be 35 origins and 20 destinations or 25 origins and 25 destinations for async API. ,
Required: True ,
}
{
origins:
{
Description: A valid `GeoJSON MultiPoint` geometry type. Please refer to [RFC 7946](https://tools.ietf.org/html/rfc7946#section-3.1.3) for details. ,
Required: False ,
}
object ,
destinations:
{
Description: A valid `GeoJSON MultiPoint` geometry type. Please refer to [RFC 7946](https://tools.ietf.org/html/rfc7946#section-3.1.3) for details. ,
Required: False ,
}
object ,
}
,
}

⚐ Response (200)

{
formatVersion:
{
Description: Format Version property ,
Required: False ,
}
string ,
matrix:
{
Description: Results as a 2 dimensional array of route summaries. ,
Required: False ,
}
[
{
statusCode:
{
Description: StatusCode property for the current cell in the input matrix. ,
Required: False ,
}
integer ,
response:
{
Description: Response object of the current cell in the input matrix. ,
Required: False ,
}
{
routeSummary:
{
Description: Summary object for route section. ,
Required: False ,
}
{
lengthInMeters:
{
Description: Length In Meters property ,
Required: False ,
}
integer ,
travelTimeInSeconds:
{
Description: Estimated travel time in seconds property that includes the delay due to real-time traffic. Note that even when traffic=false travelTimeInSeconds still includes the delay due to traffic. If DepartAt is in the future, travel time is calculated using time-dependent historic traffic data. ,
Required: False ,
}
integer ,
trafficDelayInSeconds:
{
Description: Estimated delay in seconds caused by the real-time incident(s) according to traffic information. For routes planned with departure time in the future, delays is always 0. To return additional travel times using different types of traffic information, parameter computeTravelTimeFor=all needs to be added. ,
Required: False ,
}
integer ,
departureTime:
{
Description: The estimated departure time for the route or leg. Time is in UTC. ,
Format: date-time ,
Required: False ,
}
string ,
arrivalTime:
{
Description: The estimated arrival time for the route or leg. Time is in UTC. ,
Format: date-time ,
Required: False ,
}
string ,
noTrafficTravelTimeInSeconds:
{
Description: Estimated travel time calculated as if there are no delays on the route due to traffic conditions (e.g. congestion). Included only if computeTravelTimeFor = all is used in the query. ,
Required: False ,
}
integer ,
historicTrafficTravelTimeInSeconds:
{
Description: Estimated travel time calculated using time-dependent historic traffic data. Included only if computeTravelTimeFor = all is used in the query. ,
Required: False ,
}
integer ,
liveTrafficIncidentsTravelTimeInSeconds:
{
Description: Estimated travel time calculated using real-time speed data. Included only if computeTravelTimeFor = all is used in the query. ,
Required: False ,
}
integer ,
fuelConsumptionInLiters:
{
Description: Estimated fuel consumption in liters using the Combustion Consumption Model. Included if vehicleEngineType is set to _combustion_ and constantSpeedConsumptionInLitersPerHundredkm is specified. The value will be non-negative. ,
Format: double ,
Required: False ,
}
number ,
batteryConsumptionInkWh:
{
Description: Estimated electric energy consumption in kilowatt hours (kWh) using the Electric Consumption Model. Included if vehicleEngineType is set to electric and constantSpeedConsumptionInkWhPerHundredkm is specified. The value of batteryConsumptionInkWh includes the recuperated electric energy and can therefore be negative (which indicates gaining energy). If both maxChargeInkWh and currentChargeInkWh are specified, recuperation will be capped to ensure that the battery charge level never exceeds maxChargeInkWh. If neither maxChargeInkWh nor currentChargeInkWh are specified, unconstrained recuperation is assumed in the consumption calculation. ,
Format: double ,
Required: False ,
}
number ,
}
,
}
,
}
,
]
,
summary:
{
Description: Summary object ,
Required: False ,
}
{
successfulRoutes:
{
Description: Number of successful routes in the response. ,
Required: False ,
}
integer ,
totalRoutes:
{
Description: Total number of routes requested. Number of cells in the input matrix. ,
Required: False ,
}
integer ,
}
,
}

⚐ Response (408)

{
error:
{
Description: The error object. ,
Required: False ,
}
{
code:
{
Description: The error code. ,
Required: False ,
}
string ,
message:
{
Description: The error message. ,
Required: False ,
}
string ,
target:
{
Description: The error target. ,
Required: False ,
}
string ,
details:
{
Description: The error details. ,
Required: False ,
}
[
{
code:
{
Description: The error code. ,
Required: False ,
}
string ,
message:
{
Description: The error message. ,
Required: False ,
}
string ,
target:
{
Description: The error target. ,
Required: False ,
}
string ,
details:
{
Description: The error details. ,
Required: False ,
}
[
string ,
]
,
additionalInfo:
{
Description: The error additional info. ,
Required: False ,
}
[
{
type:
{
Description: The additional info type. ,
Required: False ,
}
string ,
info:
{
Description: The additional info. ,
Required: False ,
}
object ,
}
,
]
,
}
,
]
,
additionalInfo:
{
Description: The error additional info. ,
Required: False ,
}
[
{
type:
{
Description: The additional info type. ,
Required: False ,
}
string ,
info:
{
Description: The additional info. ,
Required: False ,
}
object ,
}
,
]
,
}
,
}

⚐ Response (default)

{
error:
{
Description: The error object. ,
Required: False ,
}
{
code:
{
Description: The error code. ,
Required: False ,
}
string ,
message:
{
Description: The error message. ,
Required: False ,
}
string ,
target:
{
Description: The error target. ,
Required: False ,
}
string ,
details:
{
Description: The error details. ,
Required: False ,
}
[
{
code:
{
Description: The error code. ,
Required: False ,
}
string ,
message:
{
Description: The error message. ,
Required: False ,
}
string ,
target:
{
Description: The error target. ,
Required: False ,
}
string ,
details:
{
Description: The error details. ,
Required: False ,
}
[
string ,
]
,
additionalInfo:
{
Description: The error additional info. ,
Required: False ,
}
[
{
type:
{
Description: The additional info type. ,
Required: False ,
}
string ,
info:
{
Description: The additional info. ,
Required: False ,
}
object ,
}
,
]
,
}
,
]
,
additionalInfo:
{
Description: The error additional info. ,
Required: False ,
}
[
{
type:
{
Description: The additional info type. ,
Required: False ,
}
string ,
info:
{
Description: The additional info. ,
Required: False ,
}
object ,
}
,
]
,
}
,
}
Route_GetRouteDirections (updated)
Description :  > [!NOTE] > > **Azure Maps Route v1 service retirement** > > The Azure Maps [Route v1](/rest/api/maps/route?view=rest-maps-1.0) service is now deprecated and will be retired on 3/31/28. To avoid service disruptions, all calls to Route v1 service will need to be updated to use [Route v2025-01-01](/rest/api/maps/route) service by 3/31/28. For more information, see [Migrate Azure Maps Route 1.0 APIs](/azure/azure-maps/migrate-route-v1-api). The `Get Route Directions` API is an HTTP `GET` request that returns a route between an origin and a destination, passing through waypoints if specified. The route takes into account factors such as current traffic and the typical road speeds on the requested day of the week and time of day. Information returned includes the distance, estimated travel time, and a representation of the route geometry. Additional routing information such as optimized waypoint order or turn by turn instructions is also available, depending on the options selected. Routing service provides a set of parameters for a detailed description of a vehicle-specific consumption model. For more information, see [Consumption Model](/azure/azure-maps/consumption-model).
Reference :  Link ¶

⚶ Changes

{
  "#id": "Route_GetRouteDirections",
  "Description": {
    "new": "\n\n> [!NOTE]\n>\n> **Azure Maps Route v1 service retirement**\n>\n> The Azure Maps [Route v1](/rest/api/maps/route?view=rest-maps-1.0) service is now deprecated and will be retired on 3/31/28. To avoid service disruptions, all calls to Route v1 service will need to be updated to use [Route v2025-01-01](/rest/api/maps/route) service by 3/31/28. For more information, see [Migrate Azure Maps Route 1.0 APIs](/azure/azure-maps/migrate-route-v1-api).\n\nThe `Get Route Directions` API is an HTTP `GET` request that returns a route between an origin and a destination, passing through waypoints if specified. The route takes into account factors such as current traffic and the typical road speeds on the requested day of the week and time of day.\n\nInformation returned includes the distance, estimated travel time, and a representation of the route geometry. Additional routing information such as optimized waypoint order or turn by turn instructions is also available, depending on the options selected.\n\nRouting service provides a set of parameters for a detailed description of a vehicle-specific consumption model. For more information, see [Consumption Model](/azure/azure-maps/consumption-model).",
    "old": "\n\nThe `Get Route Directions` API is an HTTP `GET` request that returns a route between an origin and a destination, passing through waypoints if specified. The route takes into account factors such as current traffic and the typical road speeds on the requested day of the week and time of day.\n\nInformation returned includes the distance, estimated travel time, and a representation of the route geometry. Additional routing information such as optimized waypoint order or turn by turn instructions is also available, depending on the options selected.\n\nRouting service provides a set of parameters for a detailed description of a vehicle-specific consumption model. For more information, see [Consumption Model](/azure/azure-maps/consumption-model)."
  }
}

⚼ Request

GET:  /route/directions/{format}
{
x-ms-client-id:
{
Description: Specifies which account is intended for usage in conjunction with the Microsoft Entra ID security model. It represents a unique ID for the Azure Maps account and can be retrieved from the Azure Maps management plane Account API. To use Microsoft Entra ID security in Azure Maps see the following [articles](https://aka.ms/amauthdetails) for guidance. ,
Required: False ,
}
string ,
api-version:
{
Description: Version number of Azure Maps API. ,
Required: True ,
}
string ,
format:
{
Description: Desired format of the response. Value can be either _json_ or _xml_. ,
Required: True ,
}
string ,
query:
{
Description: The Coordinates through which the route is calculated, delimited by a colon. A minimum of two coordinates is required. The first one is the origin and the last is the destination of the route. Optional coordinates in-between act as waypoints in the route. You can pass up to 150 waypoints. ,
Required: True ,
}
string ,
maxAlternatives:
{
Description: Number of desired alternative routes to be calculated. Default: 0, minimum: 0 and maximum: 5 ,
Required: False ,
}
integer ,
alternativeType:
{
Description: Controls the optimality, with respect to the given planning criteria, of the calculated alternatives compared to the reference route. ,
Required: False ,
}
string ,
minDeviationDistance:
{
Description: All alternative routes returned will follow the reference route (see section POST Requests) from the origin point of the calculateRoute request for at least this number of meters. Can only be used when reconstructing a route. The minDeviationDistance parameter cannot be used in conjunction with arriveAt ,
Required: False ,
}
integer ,
arriveAt:
{
Description: The date and time of arrival at the destination point formatted as a `dateTime` value as defined in [RFC 3339, section 5.6](https://www.rfc-editor.org/rfc/rfc3339#section-5.6), with an optional time zone offset. When a time zone offset is not specified it will be assumed to be that of the destination point. Examples: * 2023-12-19T16:39:57 * 2023-12-19T16:39:57-08:00 The `arriveAt` parameter cannot be used in conjunction with `departAt`, `minDeviationDistance` or `minDeviationTime`. ,
Format: date-time ,
Required: False ,
}
string ,
departAt:
{
Description: The date and time of departure from the origin point formatted as a `dateTime` value as defined in [RFC 3339, section 5.6](https://www.rfc-editor.org/rfc/rfc3339#section-5.6), with an optional time zone offset. When a time zone offset is not specified, it will be assumed to be that of the origin point. * Default value: now * Other value: `dateTime` Examples: * 2023-12-19T16:39:57 * 2023-12-19T16:39:57-08:00 The `departAt` parameter cannot be used in conjunction with `arriveAt`. ,
Format: date-time ,
Required: False ,
}
string ,
minDeviationTime:
{
Description: All alternative routes returned will follow the reference route (see section POST Requests) from the origin point of the calculateRoute request for at least this number of seconds. Can only be used when reconstructing a route. The minDeviationTime parameter cannot be used in conjunction with arriveAt. Default value is 0. Setting )minDeviationTime_ to a value greater than zero has the following consequences: - The origin point of the _calculateRoute_ Request must be on (or very near) the input reference route. - If this is not the case, an error is returned. - However, the origin point does not need to be at the beginning of the input reference route (it can be thought of as the current vehicle position on the reference route). - The reference route, returned as the first route in the _calculateRoute_ Response, will start at the origin point specified in the _calculateRoute_ Request. The initial part of the input reference route up until the origin point will be excluded from the Response. - The values of _minDeviationDistance_ and _minDeviationTime_ determine how far alternative routes will be guaranteed to follow the reference route from the origin point onwards. - The route must use _departAt_. - The _vehicleHeading_ is ignored. ,
Required: False ,
}
integer ,
instructionsType:
{
Description: If specified, guidance instructions will be returned. Note that the instructionsType parameter cannot be used in conjunction with routeRepresentation=none. ,
Required: False ,
}
string ,
language:
{
Description: The language parameter determines the language of the guidance messages. Proper nouns (the names of streets, plazas, etc.) are returned in the specified language, or if that is not available, they are returned in an available language that is close to it. Allowed values are (a subset of) the IETF language tags. The currently supported languages are listed in the [Supported languages section](https://docs.microsoft.com/azure/azure-maps/supported-languages). Default value: en-GB ,
Required: False ,
}
string ,
computeBestOrder:
{
Description: Re-order the route waypoints using a fast heuristic algorithm to reduce the route length. Yields best results when used in conjunction with routeType _shortest_. Notice that origin and destination are excluded from the optimized waypoint indices. To include origin and destination in the response, please increase all the indices by 1 to account for the origin, and then add the destination as the final index. Possible values are true or false. True computes a better order if possible, but is not allowed to be used in conjunction with maxAlternatives value greater than 0 or in conjunction with circle waypoints. False will use the locations in the given order and not allowed to be used in conjunction with routeRepresentation _none_. ,
Required: False ,
}
boolean ,
routeRepresentation:
{
Description: Specifies the representation of the set of routes provided as response. ,
Required: False ,
}
string ,
computeTravelTimeFor:
{
Description: Specifies whether to return additional travel times using different types of traffic information (none, historic, live) as well as the default best-estimate travel time. ,
Required: False ,
}
string ,
vehicleHeading:
{
Description: The directional heading of the vehicle in degrees starting at true North and continuing in clockwise direction. North is 0 degrees, east is 90 degrees, south is 180 degrees, west is 270 degrees. Possible values 0-359 ,
Required: False ,
}
integer ,
report:
{
Description: Specifies which data should be reported for diagnosis purposes. The only possible value is _effectiveSettings_. Reports the effective parameters or data used when calling the API. In the case of defaulted parameters the default will be reflected where the parameter was not specified by the caller. ,
Required: False ,
}
string ,
sectionType:
{
Description: Specifies which of the section types is reported in the route response.

For example if sectionType = pedestrian the sections which are suited for pedestrians only are returned. Can be specified multiple times in one request, for example, '§ionType=carTrain§ionType=pedestrian§ionType=motorway'. The default sectionType refers to the travelMode input. By default travelMode is set to car ,
Required: False ,
}
array ,
vehicleAxleWeight:
{
Description: Weight per axle of the vehicle in kg. A value of 0 means that weight restrictions per axle are not considered. ,
Required: False ,
}
integer ,
vehicleWidth:
{
Description: Width of the vehicle in meters. A value of 0 means that width restrictions are not considered. ,
Format: double ,
Required: False ,
}
number ,
vehicleHeight:
{
Description: Height of the vehicle in meters. A value of 0 means that height restrictions are not considered. ,
Format: double ,
Required: False ,
}
number ,
vehicleLength:
{
Description: Length of the vehicle in meters. A value of 0 means that length restrictions are not considered. ,
Format: double ,
Required: False ,
}
number ,
vehicleMaxSpeed:
{
Description: Maximum speed of the vehicle in km/hour. The max speed in the vehicle profile is used to check whether a vehicle is allowed on motorways. * A value of 0 means that an appropriate value for the vehicle will be determined and applied during route planning. * A non-zero value may be overridden during route planning. For example, the current traffic flow is 60 km/hour. If the vehicle maximum speed is set to 50 km/hour, the routing engine will consider 60 km/hour as this is the current situation. If the maximum speed of the vehicle is provided as 80 km/hour but the current traffic flow is 60 km/hour, then routing engine will again use 60 km/hour. ,
Required: False ,
}
integer ,
vehicleWeight:
{
Description: Weight of the vehicle in kilograms. * It is mandatory if any of the *Efficiency parameters are set. * It must be strictly positive when used in the context of the Consumption Model. Weight restrictions are considered. * If no detailed **Consumption Model** is specified and the value of **vehicleWeight** is non-zero, then weight restrictions are considered. * In all other cases, this parameter is ignored. Sensible Values : for **Combustion Model** : 1600, for **Electric Model** : 1900 ,
Required: False ,
}
integer ,
vehicleCommercial:
{
Description: Whether the vehicle is used for commercial purposes. Commercial vehicles may not be allowed to drive on some roads. ,
Required: False ,
}
boolean ,
windingness:
{
Description: Level of turns for thrilling route. This parameter can only be used in conjunction with `routeType`=thrilling. ,
Required: False ,
}
string ,
hilliness:
{
Description: Degree of hilliness for thrilling route. This parameter can only be used in conjunction with `routeType`=thrilling. ,
Required: False ,
}
string ,
travelMode:
{
Description: The mode of travel for the requested route. If not defined, default is 'car'. Note that the requested travelMode may not be available for the entire route. Where the requested travelMode is not available for a particular section, the travelMode element of the response for that section will be "other". Note that travel modes bus, motorcycle, taxi and van are BETA functionality. Full restriction data is not available in all areas. ,
Required: False ,
}
string ,
avoid:
{
Description: Specifies something that the route calculation should try to avoid when determining the route. Can be specified multiple times in one request, for example, '&avoid=motorways&avoid=tollRoads&avoid=ferries'. In Route Range requests, the value alreadyUsedRoads must not be used. ,
Required: False ,
}
array ,
traffic:
{
Description: Possible values: * true - Do consider all available traffic information during routing * false - Ignore current traffic data during routing. Note that although the current traffic data is ignored during routing, the effect of historic traffic on effective road speeds is still incorporated. ,
Required: False ,
}
boolean ,
routeType:
{
Description: The type of route requested. ,
Required: False ,
}
string ,
vehicleLoadType:
{
Description: Types of cargo that may be classified as hazardous materials and restricted from some roads. Available vehicleLoadType values are US Hazmat classes 1 through 9, plus generic classifications for use in other countries/regions. Values beginning with USHazmat are for US routing while otherHazmat should be used for all other countries/regions. vehicleLoadType can be specified multiple times. This parameter is currently only considered for travelMode=truck. ,
Required: False ,
}
string ,
vehicleEngineType:
{
Description: Engine type of the vehicle. When a detailed Consumption Model is specified, it must be consistent with the value of **vehicleEngineType**. ,
Required: False ,
}
string ,
constantSpeedConsumptionInLitersPerHundredkm:
{
Description: Specifies the speed-dependent component of consumption. Provided as an unordered list of colon-delimited speed & consumption-rate pairs. The list defines points on a consumption curve. Consumption rates for speeds not in the list are found as follows: * by linear interpolation, if the given speed lies in between two speeds in the list * by linear extrapolation otherwise, assuming a constant (ΔConsumption/ΔSpeed) determined by the nearest two points in the list The list must contain between 1 and 25 points (inclusive), and may not contain duplicate points for the same speed. If it only contains a single point, then the consumption rate of that point is used without further processing. Consumption specified for the largest speed must be greater than or equal to that of the penultimate largest speed. This ensures that extrapolation does not lead to negative consumption rates. Similarly, consumption values specified for the two smallest speeds in the list cannot lead to a negative consumption rate for any smaller speed. The valid range for the consumption values(expressed in l/100km) is between 0.01 and 100000.0. Sensible Values : 50,6.3:130,11.5 **Note** : This parameter is required for **The Combustion Consumption Model**. ,
Required: False ,
}
string ,
currentFuelInLiters:
{
Description: Specifies the current supply of fuel in liters. Sensible Values : 55 ,
Format: double ,
Required: False ,
}
number ,
auxiliaryPowerInLitersPerHour:
{
Description: Specifies the amount of fuel consumed for sustaining auxiliary systems of the vehicle, in liters per hour. It can be used to specify consumption due to devices and systems such as AC systems, radio, heating, etc. Sensible Values : 0.2 ,
Format: double ,
Required: False ,
}
number ,
fuelEnergyDensityInMJoulesPerLiter:
{
Description: Specifies the amount of chemical energy stored in one liter of fuel in megajoules (MJ). It is used in conjunction with the ***Efficiency** parameters for conversions between saved or consumed energy and fuel. For example, energy density is 34.2 MJ/l for gasoline, and 35.8 MJ/l for Diesel fuel. This parameter is required if any ***Efficiency** parameter is set. Sensible Values : 34.2 ,
Format: double ,
Required: False ,
}
number ,
accelerationEfficiency:
{
Description: Specifies the efficiency of converting chemical energy stored in fuel to kinetic energy when the vehicle accelerates _(i.e. KineticEnergyGained/ChemicalEnergyConsumed). ChemicalEnergyConsumed_ is obtained by converting consumed fuel to chemical energy using **fuelEnergyDensityInMJoulesPerLiter**. Must be paired with **decelerationEfficiency**. The range of values allowed are 0.0 to 1/**decelerationEfficiency**. Sensible Values : for **Combustion Model** : 0.33, for **Electric Model** : 0.66 ,
Format: double ,
Required: False ,
}
number ,
decelerationEfficiency:
{
Description: Specifies the efficiency of converting kinetic energy to saved (not consumed) fuel when the vehicle decelerates _(i.e. ChemicalEnergySaved/KineticEnergyLost). ChemicalEnergySaved_ is obtained by converting saved (not consumed) fuel to energy using **fuelEnergyDensityInMJoulesPerLiter**. Must be paired with **accelerationEfficiency**. The range of values allowed are 0.0 to 1/**accelerationEfficiency**. Sensible Values : for **Combustion Model** : 0.83, for **Electric Model** : 0.91 ,
Format: double ,
Required: False ,
}
number ,
uphillEfficiency:
{
Description: Specifies the efficiency of converting chemical energy stored in fuel to potential energy when the vehicle gains elevation _(i.e. PotentialEnergyGained/ChemicalEnergyConsumed). ChemicalEnergyConsumed_ is obtained by converting consumed fuel to chemical energy using **fuelEnergyDensityInMJoulesPerLiter**. Must be paired with **downhillEfficiency**. The range of values allowed are 0.0 to 1/**downhillEfficiency**. Sensible Values : for **Combustion Model** : 0.27, for **Electric Model** : 0.74 ,
Format: double ,
Required: False ,
}
number ,
downhillEfficiency:
{
Description: Specifies the efficiency of converting potential energy to saved (not consumed) fuel when the vehicle loses elevation _(i.e. ChemicalEnergySaved/PotentialEnergyLost). ChemicalEnergySaved_ is obtained by converting saved (not consumed) fuel to energy using **fuelEnergyDensityInMJoulesPerLiter**. Must be paired with **uphillEfficiency**. The range of values allowed are 0.0 to 1/**uphillEfficiency**. Sensible Values : for **Combustion Model** : 0.51, for **Electric Model** : 0.73 ,
Format: double ,
Required: False ,
}
number ,
constantSpeedConsumptionInkWhPerHundredkm:
{
Description: Specifies the speed-dependent component of consumption. Provided as an unordered list of speed/consumption-rate pairs. The list defines points on a consumption curve. Consumption rates for speeds not in the list are found as follows: * by linear interpolation, if the given speed lies in between two speeds in the list * by linear extrapolation otherwise, assuming a constant (ΔConsumption/ΔSpeed) determined by the nearest two points in the list The list must contain between 1 and 25 points (inclusive), and may not contain duplicate points for the same speed. If it only contains a single point, then the consumption rate of that point is used without further processing. Consumption specified for the largest speed must be greater than or equal to that of the penultimate largest speed. This ensures that extrapolation does not lead to negative consumption rates. Similarly, consumption values specified for the two smallest speeds in the list cannot lead to a negative consumption rate for any smaller speed. The valid range for the consumption values(expressed in kWh/100km) is between 0.01 and 100000.0. Sensible Values : 50,8.2:130,21.3 This parameter is required for **Electric consumption model**. ,
Required: False ,
}
string ,
currentChargeInkWh:
{
Description: Specifies the current electric energy supply in kilowatt hours (kWh). This parameter co-exists with **maxChargeInkWh** parameter. The range of values allowed are 0.0 to **maxChargeInkWh**. Sensible Values : 43 ,
Format: double ,
Required: False ,
}
number ,
maxChargeInkWh:
{
Description: Specifies the maximum electric energy supply in kilowatt hours (kWh) that may be stored in the vehicle's battery. This parameter co-exists with **currentChargeInkWh** parameter. Minimum value has to be greater than or equal to **currentChargeInkWh**. Sensible Values : 85 ,
Format: double ,
Required: False ,
}
number ,
auxiliaryPowerInkW:
{
Description: Specifies the amount of power consumed for sustaining auxiliary systems, in kilowatts (kW). It can be used to specify consumption due to devices and systems such as AC systems, radio, heating, etc. Sensible Values : 1.7 ,
Format: double ,
Required: False ,
}
number ,
}

⚐ Response (200)

{
formatVersion:
{
Description: Format Version property ,
Required: False ,
}
string ,
routes:
{
Description: Routes array ,
Required: False ,
}
[
{
summary:
{
Description: Summary object ,
Required: False ,
}
{
lengthInMeters:
{
Description: Length In Meters property ,
Required: False ,
}
integer ,
travelTimeInSeconds:
{
Description: Estimated travel time in seconds property that includes the delay due to real-time traffic. Note that even when traffic=false travelTimeInSeconds still includes the delay due to traffic. If DepartAt is in the future, travel time is calculated using time-dependent historic traffic data. ,
Required: False ,
}
integer ,
trafficDelayInSeconds:
{
Description: Estimated delay in seconds caused by the real-time incident(s) according to traffic information. For routes planned with departure time in the future, delays is always 0. To return additional travel times using different types of traffic information, parameter computeTravelTimeFor=all needs to be added. ,
Required: False ,
}
integer ,
departureTime:
{
Description: The estimated departure time for the route or leg. Time is in UTC. ,
Format: date-time ,
Required: False ,
}
string ,
arrivalTime:
{
Description: The estimated arrival time for the route or leg. Time is in UTC. ,
Format: date-time ,
Required: False ,
}
string ,
}
,
legs:
{
Description: Legs array ,
Required: False ,
}
[
{
summary:
{
Description: Summary object for route section. ,
Required: False ,
}
{
lengthInMeters:
{
Description: Length In Meters property ,
Required: False ,
}
integer ,
travelTimeInSeconds:
{
Description: Estimated travel time in seconds property that includes the delay due to real-time traffic. Note that even when traffic=false travelTimeInSeconds still includes the delay due to traffic. If DepartAt is in the future, travel time is calculated using time-dependent historic traffic data. ,
Required: False ,
}
integer ,
trafficDelayInSeconds:
{
Description: Estimated delay in seconds caused by the real-time incident(s) according to traffic information. For routes planned with departure time in the future, delays is always 0. To return additional travel times using different types of traffic information, parameter computeTravelTimeFor=all needs to be added. ,
Required: False ,
}
integer ,
departureTime:
{
Description: The estimated departure time for the route or leg. Time is in UTC. ,
Format: date-time ,
Required: False ,
}
string ,
arrivalTime:
{
Description: The estimated arrival time for the route or leg. Time is in UTC. ,
Format: date-time ,
Required: False ,
}
string ,
noTrafficTravelTimeInSeconds:
{
Description: Estimated travel time calculated as if there are no delays on the route due to traffic conditions (e.g. congestion). Included only if computeTravelTimeFor = all is used in the query. ,
Required: False ,
}
integer ,
historicTrafficTravelTimeInSeconds:
{
Description: Estimated travel time calculated using time-dependent historic traffic data. Included only if computeTravelTimeFor = all is used in the query. ,
Required: False ,
}
integer ,
liveTrafficIncidentsTravelTimeInSeconds:
{
Description: Estimated travel time calculated using real-time speed data. Included only if computeTravelTimeFor = all is used in the query. ,
Required: False ,
}
integer ,
fuelConsumptionInLiters:
{
Description: Estimated fuel consumption in liters using the Combustion Consumption Model. Included if vehicleEngineType is set to _combustion_ and constantSpeedConsumptionInLitersPerHundredkm is specified. The value will be non-negative. ,
Format: double ,
Required: False ,
}
number ,
batteryConsumptionInkWh:
{
Description: Estimated electric energy consumption in kilowatt hours (kWh) using the Electric Consumption Model. Included if vehicleEngineType is set to electric and constantSpeedConsumptionInkWhPerHundredkm is specified. The value of batteryConsumptionInkWh includes the recuperated electric energy and can therefore be negative (which indicates gaining energy). If both maxChargeInkWh and currentChargeInkWh are specified, recuperation will be capped to ensure that the battery charge level never exceeds maxChargeInkWh. If neither maxChargeInkWh nor currentChargeInkWh are specified, unconstrained recuperation is assumed in the consumption calculation. ,
Format: double ,
Required: False ,
}
number ,
}
,
points:
{
Description: Points array ,
Required: False ,
}
[
{
latitude:
{
Description: Latitude property ,
Format: double ,
Required: False ,
}
number ,
longitude:
{
Description: Longitude property ,
Format: double ,
Required: False ,
}
number ,
}
,
]
,
}
,
]
,
sections:
{
Description: Sections array ,
Required: False ,
}
[
{
startPointIndex:
{
Description: Index of the first point (offset 0) in the route this section applies to. ,
Required: False ,
}
integer ,
endPointIndex:
{
Description: Index of the last point (offset 0) in the route this section applies to. ,
Required: False ,
}
integer ,
sectionType:
{
Description: Section types of the reported route response ,
Enum:
{
CAR_TRAIN: Sections of the route that are cars or trains. ,
COUNTRY: Sections indicating which countries/regions the route is in. ,
FERRY: Sections of the route that are ferries. ,
MOTORWAY: Sections of the route that are motorways. ,
PEDESTRIAN: Sections of the route that are only suited for pedestrians. ,
TOLL_ROAD: Sections of the route that require a toll to be payed. ,
TOLL_VIGNETTE: Sections of the route that require a toll vignette to be present. ,
TRAFFIC: Sections of the route that contain traffic information. ,
TRAVEL_MODE: Sections in relation to the request parameter `travelMode`. ,
TUNNEL: Sections of the route that are tunnels. ,
CARPOOL: Sections of the route that require use of carpool (HOV/High Occupancy Vehicle) lanes. ,
URBAN: Sections of the route that are located within urban areas. ,
}
,
Required: False ,
}
enum ,
travelMode:
{
Description: Travel mode for the calculated route. The value will be set to `other` if the requested mode of transport is not possible in this section ,
Enum:
{
car: The returned routes are optimized for cars. ,
truck: The returned routes are optimized for commercial vehicles, like for trucks. ,
taxi: The returned routes are optimized for taxis. BETA functionality. ,
bus: The returned routes are optimized for buses, including the use of bus only lanes. BETA functionality. ,
van: The returned routes are optimized for vans. BETA functionality. ,
motorcycle: The returned routes are optimized for motorcycles. BETA functionality. ,
bicycle: The returned routes are optimized for bicycles, including use of bicycle lanes. ,
pedestrian: The returned routes are optimized for pedestrians, including the use of sidewalks. ,
other: The given mode of transport is not possible in this section ,
}
,
Required: False ,
}
enum ,
simpleCategory:
{
Description: Type of the incident. Can currently be JAM, ROAD_WORK, ROAD_CLOSURE, or OTHER. See "tec" for detailed information. ,
Enum:
{
JAM: Traffic jam. ,
ROAD_WORK: Road work. ,
ROAD_CLOSURE: Road closure. ,
OTHER: Other. ,
}
,
Required: False ,
}
enum ,
effectiveSpeedInKmh:
{
Description: Effective speed of the incident in km/h, averaged over its entire length. ,
Required: False ,
}
integer ,
delayInSeconds:
{
Description: Delay in seconds caused by the incident. ,
Required: False ,
}
integer ,
magnitudeOfDelay:
{
Description: The magnitude of delay caused by the incident. These values correspond to the values of the response field ty of the [Get Traffic Incident Detail API](https://docs.microsoft.com/rest/api/maps/traffic/gettrafficincidentdetail). ,
Enum:
{
0: Unknown. ,
1: Minor. ,
2: Moderate. ,
3: Major. ,
4: Undefined, used for road closures and other indefinite delays. ,
}
,
Required: False ,
}
enum ,
tec:
{
Description: Details of the traffic event, using definitions in the [TPEG2-TEC](https://www.iso.org/standard/63116.html) standard. Can contain effectCode and causes elements. ,
Required: False ,
}
{
effectCode:
{
Description: The effect on the traffic flow. Contains a value in the tec001:EffectCode table, as defined in the [TPEG2-TEC](https://www.iso.org/standard/63116.html) standard. Can be used to color-code traffic events according to severity. ,
Required: False ,
}
integer ,
causes:
{
Description: Causes array ,
Required: False ,
}
[
{
mainCauseCode:
{
Description: The main cause of the traffic event. Contains a value in the tec002:CauseCode table, as defined in the [TPEG2-TEC](https://www.iso.org/standard/63116.html) standard. ,
Required: False ,
}
integer ,
subCauseCode:
{
Description: The subcause of the traffic event. Contains a value in the sub cause table defined by the mainCauseCode, as defined in the [TPEG2-TEC](https://www.iso.org/standard/63116.html) standard. ,
Required: False ,
}
integer ,
}
,
]
,
}
,
}
,
]
,
guidance:
{
Description: Contains guidance related elements. This field is present only when guidance was requested and is available. ,
Required: False ,
}
{
instructions:
{
Description: A list of instructions describing maneuvers. ,
Required: False ,
}
[
{
routeOffsetInMeters:
{
Description: Distance from the start of the route to the point of the instruction. ,
Required: False ,
}
integer ,
travelTimeInSeconds:
{
Description: Estimated travel time up to the point corresponding to routeOffsetInMeters. ,
Required: False ,
}
integer ,
point:
{
Description: A location represented as a latitude and longitude. ,
Required: False ,
}
{
latitude:
{
Description: Latitude property ,
Format: double ,
Required: False ,
}
number ,
longitude:
{
Description: Longitude property ,
Format: double ,
Required: False ,
}
number ,
}
,
pointIndex:
{
Description: The index of the point in the list of polyline "points" corresponding to the point of the instruction. ,
Required: False ,
}
integer ,
instructionType:
{
Description: Type of the instruction, e.g., turn or change of road form. ,
Enum:
{
TURN: Turn. ,
ROAD_CHANGE: Road Change. ,
LOCATION_DEPARTURE: Departure location. ,
LOCATION_ARRIVAL: Arrival location. ,
DIRECTION_INFO: Direction information. ,
LOCATION_WAYPOINT: Way point location. ,
}
,
Required: False ,
}
enum ,
roadNumbers:
{
Description: The road number(s) of the next significant road segment(s) after the maneuver, or of the road(s) to be followed. Example: ["E34", "N205"] ,
Required: False ,
}
[
string ,
]
,
exitNumber:
{
Description: The number(s) of a highway exit taken by the current maneuver. If an exit has multiple exit numbers, they will be separated by "," and possibly aggregated by "-", e.g., "10, 13-15". ,
Required: False ,
}
string ,
street:
{
Description: Street name of the next significant road segment after the maneuver, or of the street that should be followed. ,
Required: False ,
}
string ,
signpostText:
{
Description: The text on a signpost which is most relevant to the maneuver, or to the direction that should be followed. ,
Required: False ,
}
string ,
countryCode:
{
Description: 3-character [ISO 3166-1](https://www.iso.org/iso-3166-country-codes.html) alpha-3 country code. E.g. USA. ,
Required: False ,
}
string ,
stateCode:
{
Description: A subdivision (e.g., state) of the country, represented by the second part of an [ISO 3166-2](https://www.iso.org/standard/63546.html) code. This is only available for some countries/regions like the US, Canada, and Mexico. ,
Required: False ,
}
string ,
junctionType:
{
Description: The type of the junction where the maneuver takes place. For larger roundabouts, two separate instructions are generated for entering and leaving the roundabout. ,
Enum:
{
REGULAR: regular ,
ROUNDABOUT: roundabout ,
BIFURCATION: bifurcation ,
}
,
Required: False ,
}
enum ,
turnAngleInDecimalDegrees:
{
Description: Indicates the direction of an instruction. If junctionType indicates a turn instruction: * 180 = U-turn * [-179, -1] = Left turn * 0 = Straight on (a '0 degree' turn) * [1, 179] = Right turn If junctionType indicates a bifurcation instruction: * <0 - keep left * \>0 - keep right ,
Required: False ,
}
integer ,
roundaboutExitNumber:
{
Description: This indicates which exit to take at a roundabout. ,
Format: int64 ,
Required: False ,
}
integer ,
possibleCombineWithNext:
{
Description: It is possible to optionally combine the instruction with the next one. This can be used to build messages like "Turn left and then turn right". ,
Required: False ,
}
boolean ,
drivingSide:
{
Description: Indicates left-hand vs. right-hand side driving at the point of the maneuver. ,
Enum:
{
LEFT: Left side. ,
RIGHT: Right side. ,
}
,
Required: False ,
}
enum ,
maneuver:
{
Description: A code identifying the maneuver. ,
Enum:
{
ARRIVE: You have arrived. ,
ARRIVE_LEFT: You have arrived. Your destination is on the left. ,
ARRIVE_RIGHT: You have arrived. Your destination is on the right. ,
DEPART: Leave. ,
STRAIGHT: Keep straight on. ,
KEEP_RIGHT: Keep right. ,
BEAR_RIGHT: Bear right. ,
TURN_RIGHT: Turn right. ,
SHARP_RIGHT: Turn sharp right. ,
KEEP_LEFT: Keep left. ,
BEAR_LEFT: Bear left. ,
TURN_LEFT: Turn left. ,
SHARP_LEFT: Turn sharp left. ,
MAKE_UTURN: Make a U-turn. ,
ENTER_MOTORWAY: Take the motorway. ,
ENTER_FREEWAY: Take the freeway. ,
ENTER_HIGHWAY: Take the highway. ,
TAKE_EXIT: Take the exit. ,
MOTORWAY_EXIT_LEFT: Take the left exit. ,
MOTORWAY_EXIT_RIGHT: Take the right exit. ,
TAKE_FERRY: Take the ferry. ,
ROUNDABOUT_CROSS: Cross the roundabout. ,
ROUNDABOUT_RIGHT: At the roundabout take the exit on the right. ,
ROUNDABOUT_LEFT: At the roundabout take the exit on the left. ,
ROUNDABOUT_BACK: Go around the roundabout. ,
TRY_MAKE_UTURN: Try to make a U-turn. ,
FOLLOW: Follow. ,
SWITCH_PARALLEL_ROAD: Switch to the parallel road. ,
SWITCH_MAIN_ROAD: Switch to the main road. ,
ENTRANCE_RAMP: Take the ramp. ,
WAYPOINT_LEFT: You have reached the waypoint. It is on the left. ,
WAYPOINT_RIGHT: You have reached the waypoint. It is on the right. ,
WAYPOINT_REACHED: You have reached the waypoint. ,
}
,
Required: False ,
}
enum ,
message:
{
Description: A human-readable message for the maneuver. ,
Required: False ,
}
string ,
combinedMessage:
{
Description: A human-readable message for the maneuver combined with the message from the next instruction. Sometimes it is possible to combine two successive instructions into a single instruction making it easier to follow. When this is the case the possibleCombineWithNext flag will be true. For example: ``` 10. Turn left onto Einsteinweg/A10/E22 towards Ring Amsterdam 11. Follow Einsteinweg/A10/E22 towards Ring Amsterdam ``` The possibleCombineWithNext flag on instruction 10 is true. This indicates to the clients of coded guidance that it can be combined with instruction 11. The instructions will be combined automatically for clients requesting human-readable guidance. The combinedMessage field contains the combined message: ``` Turn left onto Einsteinweg/A10/E22 towards Ring Amsterdam then follow Einsteinweg/A10/E22 towards Ring Amsterdam. ``` ,
Required: False ,
}
string ,
}
,
]
,
instructionGroups:
{
Description: Groups a sequence of instruction elements which are related to each other. ,
Required: False ,
}
[
{
firstInstructionIndex:
{
Description: Index of the first instruction in the instructions and belonging to this group. ,
Required: False ,
}
integer ,
lastInstructionIndex:
{
Description: Index of the last instruction in the instructions and belonging to this group. ,
Required: False ,
}
integer ,
groupLengthInMeters:
{
Description: Length of the group. ,
Required: False ,
}
integer ,
groupMessage:
{
Description: Summary message when human-readable text messages are requested for guidance (instructionType=text or tagged). ,
Required: False ,
}
string ,
}
,
]
,
}
,
}
,
]
,
optimizedWaypoints:
{
Description: Optimized sequence of waypoints. It shows the index from the user provided waypoint sequence for the original and optimized list. For instance, a response: ``` ``` means that the original sequence is [0, 1, 2] and optimized sequence is [1, 2, 0]. Since the index starts by 0 the original is "first, second, third" while the optimized is "second, third, first". ,
Required: False ,
}
[
{
providedIndex:
{
Description: Way point index provided by the user. ,
Required: False ,
}
integer ,
optimizedIndex:
{
Description: Optimized way point index from the system. ,
Required: False ,
}
integer ,
}
,
]
,
report:
{
Description: Reports the effective settings used in the current call. ,
Required: False ,
}
{
effectiveSettings:
{
Description: Effective parameters or data used when calling this Route API. ,
Required: False ,
}
[
{
key:
{
Description: Name of the parameter used. ,
Required: False ,
}
string ,
value:
{
Description: Value of the parameter used. ,
Required: False ,
}
string ,
}
,
]
,
}
,
}

⚐ Response (default)

{
error:
{
Description: The error object. ,
Required: False ,
}
{
code:
{
Description: The error code. ,
Required: False ,
}
string ,
message:
{
Description: The error message. ,
Required: False ,
}
string ,
target:
{
Description: The error target. ,
Required: False ,
}
string ,
details:
{
Description: The error details. ,
Required: False ,
}
[
{
code:
{
Description: The error code. ,
Required: False ,
}
string ,
message:
{
Description: The error message. ,
Required: False ,
}
string ,
target:
{
Description: The error target. ,
Required: False ,
}
string ,
details:
{
Description: The error details. ,
Required: False ,
}
[
string ,
]
,
additionalInfo:
{
Description: The error additional info. ,
Required: False ,
}
[
{
type:
{
Description: The additional info type. ,
Required: False ,
}
string ,
info:
{
Description: The additional info. ,
Required: False ,
}
object ,
}
,
]
,
}
,
]
,
additionalInfo:
{
Description: The error additional info. ,
Required: False ,
}
[
{
type:
{
Description: The additional info type. ,
Required: False ,
}
string ,
info:
{
Description: The additional info. ,
Required: False ,
}
object ,
}
,
]
,
}
,
}
Route_PostRouteDirections (updated)
Description :  > [!NOTE] > > **Azure Maps Route v1 service retirement** > > The Azure Maps [Route v1](/rest/api/maps/route?view=rest-maps-1.0) service is now deprecated and will be retired on 3/31/28. To avoid service disruptions, all calls to Route v1 service will need to be updated to use [Route v2025-01-01](/rest/api/maps/route) service by 3/31/28. For more information, see [Migrate Azure Maps Route 1.0 APIs](/azure/azure-maps/migrate-route-v1-api). The `Post Route Directions` API is an HTTP `POST` request that returns a route between an origin and a destination, passing through waypoints if they are specified. The route will take into account factors such as current traffic and the typical road speeds on the requested day of the week and time of day. Information returned includes the distance, estimated travel time, and a representation of the route geometry. Additional routing information such as optimized waypoint order or turn by turn instructions is also available, depending on the options selected. Routing service provides a set of parameters for a detailed description of a vehicle-specific Consumption Model. Please check [Consumption Model](https://docs.microsoft.com/azure/azure-maps/consumption-model) for detailed explanation of the concepts and parameters involved.
Reference :  Link ¶

⚶ Changes

{
  "#id": "Route_PostRouteDirections",
  "Description": {
    "new": "\n\n> [!NOTE]\n>\n> **Azure Maps Route v1 service retirement**\n>\n> The Azure Maps [Route v1](/rest/api/maps/route?view=rest-maps-1.0) service is now deprecated and will be retired on 3/31/28. To avoid service disruptions, all calls to Route v1 service will need to be updated to use [Route v2025-01-01](/rest/api/maps/route) service by 3/31/28. For more information, see [Migrate Azure Maps Route 1.0 APIs](/azure/azure-maps/migrate-route-v1-api).\n\nThe `Post Route Directions` API is an HTTP `POST` request that returns a route between an origin and a destination, passing through waypoints if they are specified. The route will take into account factors such as current traffic and the typical road speeds on the requested day of the week and time of day.\n\nInformation returned includes the distance, estimated travel time, and a representation of the route geometry. Additional routing information such as optimized waypoint order or turn by turn instructions is also available, depending on the options selected.\n\nRouting service provides a set of parameters for a detailed description of a vehicle-specific Consumption Model. Please check [Consumption Model](https://docs.microsoft.com/azure/azure-maps/consumption-model) for detailed explanation of the concepts and parameters involved.",
    "old": "\n\nThe `Post Route Directions` API is an HTTP `POST` request that returns a route between an origin and a destination, passing through waypoints if they are specified. The route will take into account factors such as current traffic and the typical road speeds on the requested day of the week and time of day.\n\nInformation returned includes the distance, estimated travel time, and a representation of the route geometry. Additional routing information such as optimized waypoint order or turn by turn instructions is also available, depending on the options selected.\n\nRouting service provides a set of parameters for a detailed description of a vehicle-specific Consumption Model. Please check [Consumption Model](https://docs.microsoft.com/azure/azure-maps/consumption-model) for detailed explanation of the concepts and parameters involved."
  }
}

⚼ Request

POST:  /route/directions/{format}
{
x-ms-client-id:
{
Description: Specifies which account is intended for usage in conjunction with the Microsoft Entra ID security model. It represents a unique ID for the Azure Maps account and can be retrieved from the Azure Maps management plane Account API. To use Microsoft Entra ID security in Azure Maps see the following [articles](https://aka.ms/amauthdetails) for guidance. ,
Required: False ,
}
string ,
api-version:
{
Description: Version number of Azure Maps API. ,
Required: True ,
}
string ,
format:
{
Description: Desired format of the response. Value can be either _json_ or _xml_. ,
Required: True ,
}
string ,
query:
{
Description: The Coordinates through which the route is calculated, delimited by a colon. A minimum of two coordinates is required. The first one is the origin and the last is the destination of the route. Optional coordinates in-between act as waypoints in the route. You can pass up to 150 waypoints. ,
Required: True ,
}
string ,
maxAlternatives:
{
Description: Number of desired alternative routes to be calculated. Default: 0, minimum: 0 and maximum: 5 ,
Required: False ,
}
integer ,
alternativeType:
{
Description: Controls the optimality, with respect to the given planning criteria, of the calculated alternatives compared to the reference route. ,
Required: False ,
}
string ,
minDeviationDistance:
{
Description: All alternative routes returned will follow the reference route (see section POST Requests) from the origin point of the calculateRoute request for at least this number of meters. Can only be used when reconstructing a route. The minDeviationDistance parameter cannot be used in conjunction with arriveAt ,
Required: False ,
}
integer ,
minDeviationTime:
{
Description: All alternative routes returned will follow the reference route (see section POST Requests) from the origin point of the calculateRoute request for at least this number of seconds. Can only be used when reconstructing a route. The minDeviationTime parameter cannot be used in conjunction with arriveAt. Default value is 0. Setting )minDeviationTime_ to a value greater than zero has the following consequences: - The origin point of the _calculateRoute_ Request must be on (or very near) the input reference route. - If this is not the case, an error is returned. - However, the origin point does not need to be at the beginning of the input reference route (it can be thought of as the current vehicle position on the reference route). - The reference route, returned as the first route in the _calculateRoute_ Response, will start at the origin point specified in the _calculateRoute_ Request. The initial part of the input reference route up until the origin point will be excluded from the Response. - The values of _minDeviationDistance_ and _minDeviationTime_ determine how far alternative routes will be guaranteed to follow the reference route from the origin point onwards. - The route must use _departAt_. - The _vehicleHeading_ is ignored. ,
Required: False ,
}
integer ,
instructionsType:
{
Description: If specified, guidance instructions will be returned. Note that the instructionsType parameter cannot be used in conjunction with routeRepresentation=none. ,
Required: False ,
}
string ,
language:
{
Description: The language parameter determines the language of the guidance messages. It does not affect proper nouns (the names of streets, plazas, etc.) It has no effect when instructionsType=coded. Allowed values are (a subset of) the IETF language tags described ,
Required: False ,
}
string ,
computeBestOrder:
{
Description: Re-order the route waypoints using a fast heuristic algorithm to reduce the route length. Yields best results when used in conjunction with routeType _shortest_. Notice that origin and destination are excluded from the optimized waypoint indices. To include origin and destination in the response, please increase all the indices by 1 to account for the origin, and then add the destination as the final index. Possible values are true or false. True computes a better order if possible, but is not allowed to be used in conjunction with maxAlternatives value greater than 0 or in conjunction with circle waypoints. False will use the locations in the given order and not allowed to be used in conjunction with routeRepresentation _none_. ,
Required: False ,
}
boolean ,
routeRepresentation:
{
Description: Specifies the representation of the set of routes provided as response. ,
Required: False ,
}
string ,
computeTravelTimeFor:
{
Description: Specifies whether to return additional travel times using different types of traffic information (none, historic, live) as well as the default best-estimate travel time. ,
Required: False ,
}
string ,
vehicleHeading:
{
Description: The directional heading of the vehicle in degrees starting at true North and continuing in clockwise direction. North is 0 degrees, east is 90 degrees, south is 180 degrees, west is 270 degrees. Possible values 0-359 ,
Required: False ,
}
integer ,
report:
{
Description: Specifies which data should be reported for diagnosis purposes. The only possible value is _effectiveSettings_. Reports the effective parameters or data used when calling the API. In the case of defaulted parameters the default will be reflected where the parameter was not specified by the caller. ,
Required: False ,
}
string ,
sectionType:
{
Description: Specifies which of the section types is reported in the route response.

For example if sectionType = pedestrian the sections which are suited for pedestrians only are returned. Can be specified multiple times in one request, for example, '§ionType=carTrain§ionType=pedestrian§ionType=motorway'. The default sectionType refers to the travelMode input. By default travelMode is set to car ,
Required: False ,
}
array ,
arriveAt:
{
Description: The date and time of arrival at the destination point formatted as a `dateTime` value as defined in [RFC 3339, section 5.6](https://www.rfc-editor.org/rfc/rfc3339#section-5.6), with an optional time zone offset. When a time zone offset is not specified it will be assumed to be that of the destination point. Examples: * 2023-12-19T16:39:57 * 2023-12-19T16:39:57-08:00 The `arriveAt` parameter cannot be used in conjunction with `departAt`, `minDeviationDistance` or `minDeviationTime`. ,
Format: date-time ,
Required: False ,
}
string ,
departAt:
{
Description: The date and time of departure from the origin point formatted as a `dateTime` value as defined in [RFC 3339, section 5.6](https://www.rfc-editor.org/rfc/rfc3339#section-5.6), with an optional time zone offset. When a time zone offset is not specified, it will be assumed to be that of the origin point. * Default value: now * Other value: `dateTime` Examples: * 2023-12-19T16:39:57 * 2023-12-19T16:39:57-08:00 The `departAt` parameter cannot be used in conjunction with `arriveAt`. ,
Format: date-time ,
Required: False ,
}
string ,
vehicleAxleWeight:
{
Description: Weight per axle of the vehicle in kg. A value of 0 means that weight restrictions per axle are not considered. ,
Required: False ,
}
integer ,
vehicleLength:
{
Description: Length of the vehicle in meters. A value of 0 means that length restrictions are not considered. ,
Format: double ,
Required: False ,
}
number ,
vehicleHeight:
{
Description: Height of the vehicle in meters. A value of 0 means that height restrictions are not considered. ,
Format: double ,
Required: False ,
}
number ,
vehicleWidth:
{
Description: Width of the vehicle in meters. A value of 0 means that width restrictions are not considered. ,
Format: double ,
Required: False ,
}
number ,
vehicleMaxSpeed:
{
Description: Maximum speed of the vehicle in km/hour. The max speed in the vehicle profile is used to check whether a vehicle is allowed on motorways. * A value of 0 means that an appropriate value for the vehicle will be determined and applied during route planning. * A non-zero value may be overridden during route planning. For example, the current traffic flow is 60 km/hour. If the vehicle maximum speed is set to 50 km/hour, the routing engine will consider 60 km/hour as this is the current situation. If the maximum speed of the vehicle is provided as 80 km/hour but the current traffic flow is 60 km/hour, then routing engine will again use 60 km/hour. ,
Required: False ,
}
integer ,
vehicleWeight:
{
Description: Weight of the vehicle in kilograms. * It is mandatory if any of the *Efficiency parameters are set. * It must be strictly positive when used in the context of the Consumption Model. Weight restrictions are considered. * If no detailed **Consumption Model** is specified and the value of **vehicleWeight** is non-zero, then weight restrictions are considered. * In all other cases, this parameter is ignored. Sensible Values : for **Combustion Model** : 1600, for **Electric Model** : 1900 ,
Required: False ,
}
integer ,
vehicleCommercial:
{
Description: Whether the vehicle is used for commercial purposes. Commercial vehicles may not be allowed to drive on some roads. ,
Required: False ,
}
boolean ,
windingness:
{
Description: Level of turns for thrilling route. This parameter can only be used in conjunction with `routeType`=thrilling. ,
Required: False ,
}
string ,
hilliness:
{
Description: Degree of hilliness for thrilling route. This parameter can only be used in conjunction with `routeType`=thrilling. ,
Required: False ,
}
string ,
travelMode:
{
Description: The mode of travel for the requested route. If not defined, default is 'car'. Note that the requested travelMode may not be available for the entire route. Where the requested travelMode is not available for a particular section, the travelMode element of the response for that section will be "other". Note that travel modes bus, motorcycle, taxi and van are BETA functionality. Full restriction data is not available in all areas. ,
Required: False ,
}
string ,
avoid:
{
Description: Specifies something that the route calculation should try to avoid when determining the route. Can be specified multiple times in one request, for example, '&avoid=motorways&avoid=tollRoads&avoid=ferries'. In Route Range requests, the value alreadyUsedRoads must not be used. ,
Required: False ,
}
array ,
traffic:
{
Description: Possible values: * true - Do consider all available traffic information during routing * false - Ignore current traffic data during routing. Note that although the current traffic data is ignored during routing, the effect of historic traffic on effective road speeds is still incorporated. ,
Required: False ,
}
boolean ,
routeType:
{
Description: The type of route requested. ,
Required: False ,
}
string ,
vehicleLoadType:
{
Description: Types of cargo that may be classified as hazardous materials and restricted from some roads. Available vehicleLoadType values are US Hazmat classes 1 through 9, plus generic classifications for use in other countries/regions. Values beginning with USHazmat are for US routing while otherHazmat should be used for all other countries/regions. vehicleLoadType can be specified multiple times. This parameter is currently only considered for travelMode=truck. ,
Required: False ,
}
string ,
vehicleEngineType:
{
Description: Engine type of the vehicle. When a detailed Consumption Model is specified, it must be consistent with the value of **vehicleEngineType**. ,
Required: False ,
}
string ,
constantSpeedConsumptionInLitersPerHundredkm:
{
Description: Specifies the speed-dependent component of consumption. Provided as an unordered list of colon-delimited speed & consumption-rate pairs. The list defines points on a consumption curve. Consumption rates for speeds not in the list are found as follows: * by linear interpolation, if the given speed lies in between two speeds in the list * by linear extrapolation otherwise, assuming a constant (ΔConsumption/ΔSpeed) determined by the nearest two points in the list The list must contain between 1 and 25 points (inclusive), and may not contain duplicate points for the same speed. If it only contains a single point, then the consumption rate of that point is used without further processing. Consumption specified for the largest speed must be greater than or equal to that of the penultimate largest speed. This ensures that extrapolation does not lead to negative consumption rates. Similarly, consumption values specified for the two smallest speeds in the list cannot lead to a negative consumption rate for any smaller speed. The valid range for the consumption values(expressed in l/100km) is between 0.01 and 100000.0. Sensible Values : 50,6.3:130,11.5 **Note** : This parameter is required for **The Combustion Consumption Model**. ,
Required: False ,
}
string ,
currentFuelInLiters:
{
Description: Specifies the current supply of fuel in liters. Sensible Values : 55 ,
Format: double ,
Required: False ,
}
number ,
auxiliaryPowerInLitersPerHour:
{
Description: Specifies the amount of fuel consumed for sustaining auxiliary systems of the vehicle, in liters per hour. It can be used to specify consumption due to devices and systems such as AC systems, radio, heating, etc. Sensible Values : 0.2 ,
Format: double ,
Required: False ,
}
number ,
fuelEnergyDensityInMJoulesPerLiter:
{
Description: Specifies the amount of chemical energy stored in one liter of fuel in megajoules (MJ). It is used in conjunction with the ***Efficiency** parameters for conversions between saved or consumed energy and fuel. For example, energy density is 34.2 MJ/l for gasoline, and 35.8 MJ/l for Diesel fuel. This parameter is required if any ***Efficiency** parameter is set. Sensible Values : 34.2 ,
Format: double ,
Required: False ,
}
number ,
accelerationEfficiency:
{
Description: Specifies the efficiency of converting chemical energy stored in fuel to kinetic energy when the vehicle accelerates _(i.e. KineticEnergyGained/ChemicalEnergyConsumed). ChemicalEnergyConsumed_ is obtained by converting consumed fuel to chemical energy using **fuelEnergyDensityInMJoulesPerLiter**. Must be paired with **decelerationEfficiency**. The range of values allowed are 0.0 to 1/**decelerationEfficiency**. Sensible Values : for **Combustion Model** : 0.33, for **Electric Model** : 0.66 ,
Format: double ,
Required: False ,
}
number ,
decelerationEfficiency:
{
Description: Specifies the efficiency of converting kinetic energy to saved (not consumed) fuel when the vehicle decelerates _(i.e. ChemicalEnergySaved/KineticEnergyLost). ChemicalEnergySaved_ is obtained by converting saved (not consumed) fuel to energy using **fuelEnergyDensityInMJoulesPerLiter**. Must be paired with **accelerationEfficiency**. The range of values allowed are 0.0 to 1/**accelerationEfficiency**. Sensible Values : for **Combustion Model** : 0.83, for **Electric Model** : 0.91 ,
Format: double ,
Required: False ,
}
number ,
uphillEfficiency:
{
Description: Specifies the efficiency of converting chemical energy stored in fuel to potential energy when the vehicle gains elevation _(i.e. PotentialEnergyGained/ChemicalEnergyConsumed). ChemicalEnergyConsumed_ is obtained by converting consumed fuel to chemical energy using **fuelEnergyDensityInMJoulesPerLiter**. Must be paired with **downhillEfficiency**. The range of values allowed are 0.0 to 1/**downhillEfficiency**. Sensible Values : for **Combustion Model** : 0.27, for **Electric Model** : 0.74 ,
Format: double ,
Required: False ,
}
number ,
downhillEfficiency:
{
Description: Specifies the efficiency of converting potential energy to saved (not consumed) fuel when the vehicle loses elevation _(i.e. ChemicalEnergySaved/PotentialEnergyLost). ChemicalEnergySaved_ is obtained by converting saved (not consumed) fuel to energy using **fuelEnergyDensityInMJoulesPerLiter**. Must be paired with **uphillEfficiency**. The range of values allowed are 0.0 to 1/**uphillEfficiency**. Sensible Values : for **Combustion Model** : 0.51, for **Electric Model** : 0.73 ,
Format: double ,
Required: False ,
}
number ,
constantSpeedConsumptionInkWhPerHundredkm:
{
Description: Specifies the speed-dependent component of consumption. Provided as an unordered list of speed/consumption-rate pairs. The list defines points on a consumption curve. Consumption rates for speeds not in the list are found as follows: * by linear interpolation, if the given speed lies in between two speeds in the list * by linear extrapolation otherwise, assuming a constant (ΔConsumption/ΔSpeed) determined by the nearest two points in the list The list must contain between 1 and 25 points (inclusive), and may not contain duplicate points for the same speed. If it only contains a single point, then the consumption rate of that point is used without further processing. Consumption specified for the largest speed must be greater than or equal to that of the penultimate largest speed. This ensures that extrapolation does not lead to negative consumption rates. Similarly, consumption values specified for the two smallest speeds in the list cannot lead to a negative consumption rate for any smaller speed. The valid range for the consumption values(expressed in kWh/100km) is between 0.01 and 100000.0. Sensible Values : 50,8.2:130,21.3 This parameter is required for **Electric consumption model**. ,
Required: False ,
}
string ,
currentChargeInkWh:
{
Description: Specifies the current electric energy supply in kilowatt hours (kWh). This parameter co-exists with **maxChargeInkWh** parameter. The range of values allowed are 0.0 to **maxChargeInkWh**. Sensible Values : 43 ,
Format: double ,
Required: False ,
}
number ,
maxChargeInkWh:
{
Description: Specifies the maximum electric energy supply in kilowatt hours (kWh) that may be stored in the vehicle's battery. This parameter co-exists with **currentChargeInkWh** parameter. Minimum value has to be greater than or equal to **currentChargeInkWh**. Sensible Values : 85 ,
Format: double ,
Required: False ,
}
number ,
auxiliaryPowerInkW:
{
Description: Specifies the amount of power consumed for sustaining auxiliary systems, in kilowatts (kW). It can be used to specify consumption due to devices and systems such as AC systems, radio, heating, etc. Sensible Values : 1.7 ,
Format: double ,
Required: False ,
}
number ,
routeDirectionParameters:
{
Description: Used for reconstructing a route and for calculating zero or more alternative routes to this reference route. The provided sequence of coordinates is used as input for route reconstruction. The alternative routes are calculated between the origin and destination points specified in the base path parameter locations. If both minDeviationDistance and minDeviationTime are set to zero, then these origin and destination points are expected to be at (or very near) the beginning and end of the reference route, respectively. Intermediate locations (waypoints) are not supported when using supportingPoints. Setting at least one of minDeviationDistance or minDeviationTime to a value greater than zero has the following consequences: * The origin point of the calculateRoute request must be on (or very near) the input reference route. If this is not the case, an error is returned. However, the origin point does not need to be at the beginning of the input reference route (it can be thought of as the current vehicle position on the reference route). * The reference route, returned as the first route in the calculateRoute response, will start at the origin point specified in the calculateRoute request. The initial part of the input reference route up until the origin point will be excluded from the response. * The values of minDeviationDistance and minDeviationTime determine how far alternative routes will be guaranteed to follow the reference route from the origin point onwards. * The route must use departAt. * The vehicleHeading is ignored. ,
Required: True ,
}
{
supportingPoints:
{
Description: A GeoJSON Geometry collection representing sequence of coordinates used as input for route reconstruction and for calculating zero or more alternative routes to this reference route. - The provided sequence of supporting points is used as input for route reconstruction. - The alternative routes are calculated between the origin and destination points specified in the base path parameter locations. - If both _minDeviationDistance_ and _minDeviationTime_ are set to zero, then these origin and destination points are expected to be at (or very near) the beginning and end of the reference route, respectively. - Intermediate locations (_waypoints_) are not supported when using <_supportingPoints_>. - The reference route may contain traffic incidents of type _ROAD_CLOSURE_, which are ignored for the calculation of the reference route's travel time and traffic delay. Please refer to [Supporting Points](https://docs.microsoft.com/azure/azure-maps/how-to-use-best-practices-for-routing#calculate-and-bias-alternative-routes-using-supporting-points) for details. ,
Required: False ,
}
object ,
avoidVignette:
{
Description: This is a list of 3-character, ISO 3166-1, alpha-3 country codes of countries/regions in which all toll roads with vignettes are to be avoided, e.g. "AUS,CHE". Toll roads with vignettes in countries/regions not in the list are unaffected. Note: It is an error to specify both **avoidVignette** and **allowVignette**. ,
Required: False ,
}
[
string ,
]
,
allowVignette:
{
Description: This is a list of 3-character, ISO 3166-1, alpha-3 country codes of countries/regions in which toll roads with vignettes are allowed, e.g. "AUS,CHE". Specifying **allowVignette** with some countries/regions X is equivalent to specifying **avoidVignette** with all countries/regions but X. Specifying **allowVignette** with an empty list is the same as avoiding all toll roads with vignettes. Note: It is an error to specify both **avoidVignette** and **allowVignette**. ,
Required: False ,
}
[
string ,
]
,
avoidAreas:
{
Description: A GeoJSON MultiPolygon representing list of areas to avoid. Only rectangle polygons are supported. The maximum size of a rectangle is about 160x160 km. Maximum number of avoided areas is **10**. It cannot cross the 180th meridian. It must be between -80 and +80 degrees of latitude. ,
Required: False ,
}
object ,
}
,
}

⚐ Response (200)

{
formatVersion:
{
Description: Format Version property ,
Required: False ,
}
string ,
routes:
{
Description: Routes array ,
Required: False ,
}
[
{
summary:
{
Description: Summary object ,
Required: False ,
}
{
lengthInMeters:
{
Description: Length In Meters property ,
Required: False ,
}
integer ,
travelTimeInSeconds:
{
Description: Estimated travel time in seconds property that includes the delay due to real-time traffic. Note that even when traffic=false travelTimeInSeconds still includes the delay due to traffic. If DepartAt is in the future, travel time is calculated using time-dependent historic traffic data. ,
Required: False ,
}
integer ,
trafficDelayInSeconds:
{
Description: Estimated delay in seconds caused by the real-time incident(s) according to traffic information. For routes planned with departure time in the future, delays is always 0. To return additional travel times using different types of traffic information, parameter computeTravelTimeFor=all needs to be added. ,
Required: False ,
}
integer ,
departureTime:
{
Description: The estimated departure time for the route or leg. Time is in UTC. ,
Format: date-time ,
Required: False ,
}
string ,
arrivalTime:
{
Description: The estimated arrival time for the route or leg. Time is in UTC. ,
Format: date-time ,
Required: False ,
}
string ,
}
,
legs:
{
Description: Legs array ,
Required: False ,
}
[
{
summary:
{
Description: Summary object for route section. ,
Required: False ,
}
{
lengthInMeters:
{
Description: Length In Meters property ,
Required: False ,
}
integer ,
travelTimeInSeconds:
{
Description: Estimated travel time in seconds property that includes the delay due to real-time traffic. Note that even when traffic=false travelTimeInSeconds still includes the delay due to traffic. If DepartAt is in the future, travel time is calculated using time-dependent historic traffic data. ,
Required: False ,
}
integer ,
trafficDelayInSeconds:
{
Description: Estimated delay in seconds caused by the real-time incident(s) according to traffic information. For routes planned with departure time in the future, delays is always 0. To return additional travel times using different types of traffic information, parameter computeTravelTimeFor=all needs to be added. ,
Required: False ,
}
integer ,
departureTime:
{
Description: The estimated departure time for the route or leg. Time is in UTC. ,
Format: date-time ,
Required: False ,
}
string ,
arrivalTime:
{
Description: The estimated arrival time for the route or leg. Time is in UTC. ,
Format: date-time ,
Required: False ,
}
string ,
noTrafficTravelTimeInSeconds:
{
Description: Estimated travel time calculated as if there are no delays on the route due to traffic conditions (e.g. congestion). Included only if computeTravelTimeFor = all is used in the query. ,
Required: False ,
}
integer ,
historicTrafficTravelTimeInSeconds:
{
Description: Estimated travel time calculated using time-dependent historic traffic data. Included only if computeTravelTimeFor = all is used in the query. ,
Required: False ,
}
integer ,
liveTrafficIncidentsTravelTimeInSeconds:
{
Description: Estimated travel time calculated using real-time speed data. Included only if computeTravelTimeFor = all is used in the query. ,
Required: False ,
}
integer ,
fuelConsumptionInLiters:
{
Description: Estimated fuel consumption in liters using the Combustion Consumption Model. Included if vehicleEngineType is set to _combustion_ and constantSpeedConsumptionInLitersPerHundredkm is specified. The value will be non-negative. ,
Format: double ,
Required: False ,
}
number ,
batteryConsumptionInkWh:
{
Description: Estimated electric energy consumption in kilowatt hours (kWh) using the Electric Consumption Model. Included if vehicleEngineType is set to electric and constantSpeedConsumptionInkWhPerHundredkm is specified. The value of batteryConsumptionInkWh includes the recuperated electric energy and can therefore be negative (which indicates gaining energy). If both maxChargeInkWh and currentChargeInkWh are specified, recuperation will be capped to ensure that the battery charge level never exceeds maxChargeInkWh. If neither maxChargeInkWh nor currentChargeInkWh are specified, unconstrained recuperation is assumed in the consumption calculation. ,
Format: double ,
Required: False ,
}
number ,
}
,
points:
{
Description: Points array ,
Required: False ,
}
[
{
latitude:
{
Description: Latitude property ,
Format: double ,
Required: False ,
}
number ,
longitude:
{
Description: Longitude property ,
Format: double ,
Required: False ,
}
number ,
}
,
]
,
}
,
]
,
sections:
{
Description: Sections array ,
Required: False ,
}
[
{
startPointIndex:
{
Description: Index of the first point (offset 0) in the route this section applies to. ,
Required: False ,
}
integer ,
endPointIndex:
{
Description: Index of the last point (offset 0) in the route this section applies to. ,
Required: False ,
}
integer ,
sectionType:
{
Description: Section types of the reported route response ,
Enum:
{
CAR_TRAIN: Sections of the route that are cars or trains. ,
COUNTRY: Sections indicating which countries/regions the route is in. ,
FERRY: Sections of the route that are ferries. ,
MOTORWAY: Sections of the route that are motorways. ,
PEDESTRIAN: Sections of the route that are only suited for pedestrians. ,
TOLL_ROAD: Sections of the route that require a toll to be payed. ,
TOLL_VIGNETTE: Sections of the route that require a toll vignette to be present. ,
TRAFFIC: Sections of the route that contain traffic information. ,
TRAVEL_MODE: Sections in relation to the request parameter `travelMode`. ,
TUNNEL: Sections of the route that are tunnels. ,
CARPOOL: Sections of the route that require use of carpool (HOV/High Occupancy Vehicle) lanes. ,
URBAN: Sections of the route that are located within urban areas. ,
}
,
Required: False ,
}
enum ,
travelMode:
{
Description: Travel mode for the calculated route. The value will be set to `other` if the requested mode of transport is not possible in this section ,
Enum:
{
car: The returned routes are optimized for cars. ,
truck: The returned routes are optimized for commercial vehicles, like for trucks. ,
taxi: The returned routes are optimized for taxis. BETA functionality. ,
bus: The returned routes are optimized for buses, including the use of bus only lanes. BETA functionality. ,
van: The returned routes are optimized for vans. BETA functionality. ,
motorcycle: The returned routes are optimized for motorcycles. BETA functionality. ,
bicycle: The returned routes are optimized for bicycles, including use of bicycle lanes. ,
pedestrian: The returned routes are optimized for pedestrians, including the use of sidewalks. ,
other: The given mode of transport is not possible in this section ,
}
,
Required: False ,
}
enum ,
simpleCategory:
{
Description: Type of the incident. Can currently be JAM, ROAD_WORK, ROAD_CLOSURE, or OTHER. See "tec" for detailed information. ,
Enum:
{
JAM: Traffic jam. ,
ROAD_WORK: Road work. ,
ROAD_CLOSURE: Road closure. ,
OTHER: Other. ,
}
,
Required: False ,
}
enum ,
effectiveSpeedInKmh:
{
Description: Effective speed of the incident in km/h, averaged over its entire length. ,
Required: False ,
}
integer ,
delayInSeconds:
{
Description: Delay in seconds caused by the incident. ,
Required: False ,
}
integer ,
magnitudeOfDelay:
{
Description: The magnitude of delay caused by the incident. These values correspond to the values of the response field ty of the [Get Traffic Incident Detail API](https://docs.microsoft.com/rest/api/maps/traffic/gettrafficincidentdetail). ,
Enum:
{
0: Unknown. ,
1: Minor. ,
2: Moderate. ,
3: Major. ,
4: Undefined, used for road closures and other indefinite delays. ,
}
,
Required: False ,
}
enum ,
tec:
{
Description: Details of the traffic event, using definitions in the [TPEG2-TEC](https://www.iso.org/standard/63116.html) standard. Can contain effectCode and causes elements. ,
Required: False ,
}
{
effectCode:
{
Description: The effect on the traffic flow. Contains a value in the tec001:EffectCode table, as defined in the [TPEG2-TEC](https://www.iso.org/standard/63116.html) standard. Can be used to color-code traffic events according to severity. ,
Required: False ,
}
integer ,
causes:
{
Description: Causes array ,
Required: False ,
}
[
{
mainCauseCode:
{
Description: The main cause of the traffic event. Contains a value in the tec002:CauseCode table, as defined in the [TPEG2-TEC](https://www.iso.org/standard/63116.html) standard. ,
Required: False ,
}
integer ,
subCauseCode:
{
Description: The subcause of the traffic event. Contains a value in the sub cause table defined by the mainCauseCode, as defined in the [TPEG2-TEC](https://www.iso.org/standard/63116.html) standard. ,
Required: False ,
}
integer ,
}
,
]
,
}
,
}
,
]
,
guidance:
{
Description: Contains guidance related elements. This field is present only when guidance was requested and is available. ,
Required: False ,
}
{
instructions:
{
Description: A list of instructions describing maneuvers. ,
Required: False ,
}
[
{
routeOffsetInMeters:
{
Description: Distance from the start of the route to the point of the instruction. ,
Required: False ,
}
integer ,
travelTimeInSeconds:
{
Description: Estimated travel time up to the point corresponding to routeOffsetInMeters. ,
Required: False ,
}
integer ,
point:
{
Description: A location represented as a latitude and longitude. ,
Required: False ,
}
{
latitude:
{
Description: Latitude property ,
Format: double ,
Required: False ,
}
number ,
longitude:
{
Description: Longitude property ,
Format: double ,
Required: False ,
}
number ,
}
,
pointIndex:
{
Description: The index of the point in the list of polyline "points" corresponding to the point of the instruction. ,
Required: False ,
}
integer ,
instructionType:
{
Description: Type of the instruction, e.g., turn or change of road form. ,
Enum:
{
TURN: Turn. ,
ROAD_CHANGE: Road Change. ,
LOCATION_DEPARTURE: Departure location. ,
LOCATION_ARRIVAL: Arrival location. ,
DIRECTION_INFO: Direction information. ,
LOCATION_WAYPOINT: Way point location. ,
}
,
Required: False ,
}
enum ,
roadNumbers:
{
Description: The road number(s) of the next significant road segment(s) after the maneuver, or of the road(s) to be followed. Example: ["E34", "N205"] ,
Required: False ,
}
[
string ,
]
,
exitNumber:
{
Description: The number(s) of a highway exit taken by the current maneuver. If an exit has multiple exit numbers, they will be separated by "," and possibly aggregated by "-", e.g., "10, 13-15". ,
Required: False ,
}
string ,
street:
{
Description: Street name of the next significant road segment after the maneuver, or of the street that should be followed. ,
Required: False ,
}
string ,
signpostText:
{
Description: The text on a signpost which is most relevant to the maneuver, or to the direction that should be followed. ,
Required: False ,
}
string ,
countryCode:
{
Description: 3-character [ISO 3166-1](https://www.iso.org/iso-3166-country-codes.html) alpha-3 country code. E.g. USA. ,
Required: False ,
}
string ,
stateCode:
{
Description: A subdivision (e.g., state) of the country, represented by the second part of an [ISO 3166-2](https://www.iso.org/standard/63546.html) code. This is only available for some countries/regions like the US, Canada, and Mexico. ,
Required: False ,
}
string ,
junctionType:
{
Description: The type of the junction where the maneuver takes place. For larger roundabouts, two separate instructions are generated for entering and leaving the roundabout. ,
Enum:
{
REGULAR: regular ,
ROUNDABOUT: roundabout ,
BIFURCATION: bifurcation ,
}
,
Required: False ,
}
enum ,
turnAngleInDecimalDegrees:
{
Description: Indicates the direction of an instruction. If junctionType indicates a turn instruction: * 180 = U-turn * [-179, -1] = Left turn * 0 = Straight on (a '0 degree' turn) * [1, 179] = Right turn If junctionType indicates a bifurcation instruction: * <0 - keep left * \>0 - keep right ,
Required: False ,
}
integer ,
roundaboutExitNumber:
{
Description: This indicates which exit to take at a roundabout. ,
Format: int64 ,
Required: False ,
}
integer ,
possibleCombineWithNext:
{
Description: It is possible to optionally combine the instruction with the next one. This can be used to build messages like "Turn left and then turn right". ,
Required: False ,
}
boolean ,
drivingSide:
{
Description: Indicates left-hand vs. right-hand side driving at the point of the maneuver. ,
Enum:
{
LEFT: Left side. ,
RIGHT: Right side. ,
}
,
Required: False ,
}
enum ,
maneuver:
{
Description: A code identifying the maneuver. ,
Enum:
{
ARRIVE: You have arrived. ,
ARRIVE_LEFT: You have arrived. Your destination is on the left. ,
ARRIVE_RIGHT: You have arrived. Your destination is on the right. ,
DEPART: Leave. ,
STRAIGHT: Keep straight on. ,
KEEP_RIGHT: Keep right. ,
BEAR_RIGHT: Bear right. ,
TURN_RIGHT: Turn right. ,
SHARP_RIGHT: Turn sharp right. ,
KEEP_LEFT: Keep left. ,
BEAR_LEFT: Bear left. ,
TURN_LEFT: Turn left. ,
SHARP_LEFT: Turn sharp left. ,
MAKE_UTURN: Make a U-turn. ,
ENTER_MOTORWAY: Take the motorway. ,
ENTER_FREEWAY: Take the freeway. ,
ENTER_HIGHWAY: Take the highway. ,
TAKE_EXIT: Take the exit. ,
MOTORWAY_EXIT_LEFT: Take the left exit. ,
MOTORWAY_EXIT_RIGHT: Take the right exit. ,
TAKE_FERRY: Take the ferry. ,
ROUNDABOUT_CROSS: Cross the roundabout. ,
ROUNDABOUT_RIGHT: At the roundabout take the exit on the right. ,
ROUNDABOUT_LEFT: At the roundabout take the exit on the left. ,
ROUNDABOUT_BACK: Go around the roundabout. ,
TRY_MAKE_UTURN: Try to make a U-turn. ,
FOLLOW: Follow. ,
SWITCH_PARALLEL_ROAD: Switch to the parallel road. ,
SWITCH_MAIN_ROAD: Switch to the main road. ,
ENTRANCE_RAMP: Take the ramp. ,
WAYPOINT_LEFT: You have reached the waypoint. It is on the left. ,
WAYPOINT_RIGHT: You have reached the waypoint. It is on the right. ,
WAYPOINT_REACHED: You have reached the waypoint. ,
}
,
Required: False ,
}
enum ,
message:
{
Description: A human-readable message for the maneuver. ,
Required: False ,
}
string ,
combinedMessage:
{
Description: A human-readable message for the maneuver combined with the message from the next instruction. Sometimes it is possible to combine two successive instructions into a single instruction making it easier to follow. When this is the case the possibleCombineWithNext flag will be true. For example: ``` 10. Turn left onto Einsteinweg/A10/E22 towards Ring Amsterdam 11. Follow Einsteinweg/A10/E22 towards Ring Amsterdam ``` The possibleCombineWithNext flag on instruction 10 is true. This indicates to the clients of coded guidance that it can be combined with instruction 11. The instructions will be combined automatically for clients requesting human-readable guidance. The combinedMessage field contains the combined message: ``` Turn left onto Einsteinweg/A10/E22 towards Ring Amsterdam then follow Einsteinweg/A10/E22 towards Ring Amsterdam. ``` ,
Required: False ,
}
string ,
}
,
]
,
instructionGroups:
{
Description: Groups a sequence of instruction elements which are related to each other. ,
Required: False ,
}
[
{
firstInstructionIndex:
{
Description: Index of the first instruction in the instructions and belonging to this group. ,
Required: False ,
}
integer ,
lastInstructionIndex:
{
Description: Index of the last instruction in the instructions and belonging to this group. ,
Required: False ,
}
integer ,
groupLengthInMeters:
{
Description: Length of the group. ,
Required: False ,
}
integer ,
groupMessage:
{
Description: Summary message when human-readable text messages are requested for guidance (instructionType=text or tagged). ,
Required: False ,
}
string ,
}
,
]
,
}
,
}
,
]
,
optimizedWaypoints:
{
Description: Optimized sequence of waypoints. It shows the index from the user provided waypoint sequence for the original and optimized list. For instance, a response: ``` ``` means that the original sequence is [0, 1, 2] and optimized sequence is [1, 2, 0]. Since the index starts by 0 the original is "first, second, third" while the optimized is "second, third, first". ,
Required: False ,
}
[
{
providedIndex:
{
Description: Way point index provided by the user. ,
Required: False ,
}
integer ,
optimizedIndex:
{
Description: Optimized way point index from the system. ,
Required: False ,
}
integer ,
}
,
]
,
report:
{
Description: Reports the effective settings used in the current call. ,
Required: False ,
}
{
effectiveSettings:
{
Description: Effective parameters or data used when calling this Route API. ,
Required: False ,
}
[
{
key:
{
Description: Name of the parameter used. ,
Required: False ,
}
string ,
value:
{
Description: Value of the parameter used. ,
Required: False ,
}
string ,
}
,
]
,
}
,
}

⚐ Response (default)

{
error:
{
Description: The error object. ,
Required: False ,
}
{
code:
{
Description: The error code. ,
Required: False ,
}
string ,
message:
{
Description: The error message. ,
Required: False ,
}
string ,
target:
{
Description: The error target. ,
Required: False ,
}
string ,
details:
{
Description: The error details. ,
Required: False ,
}
[
{
code:
{
Description: The error code. ,
Required: False ,
}
string ,
message:
{
Description: The error message. ,
Required: False ,
}
string ,
target:
{
Description: The error target. ,
Required: False ,
}
string ,
details:
{
Description: The error details. ,
Required: False ,
}
[
string ,
]
,
additionalInfo:
{
Description: The error additional info. ,
Required: False ,
}
[
{
type:
{
Description: The additional info type. ,
Required: False ,
}
string ,
info:
{
Description: The additional info. ,
Required: False ,
}
object ,
}
,
]
,
}
,
]
,
additionalInfo:
{
Description: The error additional info. ,
Required: False ,
}
[
{
type:
{
Description: The additional info type. ,
Required: False ,
}
string ,
info:
{
Description: The additional info. ,
Required: False ,
}
object ,
}
,
]
,
}
,
}
Route_GetRouteRange (updated)
Description :  > [!NOTE] > > **Azure Maps Route v1 service retirement** > > The Azure Maps [Route v1](/rest/api/maps/route?view=rest-maps-1.0) service is now deprecated and will be retired on 3/31/28. To avoid service disruptions, all calls to Route v1 service will need to be updated to use [Route v2025-01-01](/rest/api/maps/route) service by 3/31/28. For more information, see [Migrate Azure Maps Route 1.0 APIs](/azure/azure-maps/migrate-route-v1-api). The `Get Route Range` (Isochrone) API is an HTTP `GET` request that will calculate a set of locations that can be reached from the origin point based on fuel, energy, time or distance budget that is specified. A polygon boundary (or Isochrone) is returned in a counterclockwise orientation as well as the precise polygon center which was the result of the origin point. The returned polygon can be used for further processing such as [Search Inside Geometry](/rest/api/maps/search/post-search-inside-geometry) to search for POIs within the provided isochrone.
Reference :  Link ¶

⚶ Changes

{
  "#id": "Route_GetRouteRange",
  "Description": {
    "new": "\n\n> [!NOTE]\n>\n> **Azure Maps Route v1 service retirement**\n>\n> The Azure Maps [Route v1](/rest/api/maps/route?view=rest-maps-1.0) service is now deprecated and will be retired on 3/31/28. To avoid service disruptions, all calls to Route v1 service will need to be updated to use [Route v2025-01-01](/rest/api/maps/route) service by 3/31/28. For more information, see [Migrate Azure Maps Route 1.0 APIs](/azure/azure-maps/migrate-route-v1-api).\n\nThe `Get Route Range` (Isochrone) API is an HTTP `GET` request that will calculate a set of locations that can be reached from the origin point based on fuel, energy, time or distance budget that is specified. A polygon boundary (or Isochrone) is returned in a counterclockwise  orientation as well as the precise polygon center which was the result of the origin point.\n\nThe returned polygon can be used for further processing such as  [Search Inside Geometry](/rest/api/maps/search/post-search-inside-geometry) to  search for POIs within the provided isochrone.",
    "old": "\n\nThe `Get Route Range` (Isochrone) API is an HTTP `GET` request that will calculate a set of locations that can be reached from the origin point based on fuel, energy, time or distance budget that is specified. A polygon boundary (or Isochrone) is returned in a counterclockwise  orientation as well as the precise polygon center which was the result of the origin point.\n\nThe returned polygon can be used for further processing such as  [Search Inside Geometry](/rest/api/maps/search/post-search-inside-geometry) to  search for POIs within the provided isochrone."
  }
}

⚼ Request

GET:  /route/range/{format}
{
x-ms-client-id:
{
Description: Specifies which account is intended for usage in conjunction with the Microsoft Entra ID security model. It represents a unique ID for the Azure Maps account and can be retrieved from the Azure Maps management plane Account API. To use Microsoft Entra ID security in Azure Maps see the following [articles](https://aka.ms/amauthdetails) for guidance. ,
Required: False ,
}
string ,
api-version:
{
Description: Version number of Azure Maps API. ,
Required: True ,
}
string ,
format:
{
Description: Desired format of the response. Value can be either _json_ or _xml_. ,
Required: True ,
}
string ,
query:
{
Description: The Coordinate from which the range calculation should start. ,
Required: True ,
}
array ,
fuelBudgetInLiters:
{
Description: Fuel budget in liters that determines maximal range which can be travelled using the specified Combustion Consumption Model.
When fuelBudgetInLiters is used, it is mandatory to specify a detailed Combustion Consumption Model.
Exactly one budget (fuelBudgetInLiters, energyBudgetInkWh, timeBudgetInSec, or distanceBudgetInMeters) must be used. ,
Format: double ,
Required: False ,
}
number ,
energyBudgetInkWh:
{
Description: Electric energy budget in kilowatt hours (kWh) that determines maximal range which can be travelled using the specified Electric Consumption Model.
When energyBudgetInkWh is used, it is mandatory to specify a detailed Electric Consumption Model.
Exactly one budget (fuelBudgetInLiters, energyBudgetInkWh, timeBudgetInSec, or distanceBudgetInMeters) must be used. ,
Format: double ,
Required: False ,
}
number ,
timeBudgetInSec:
{
Description: Time budget in seconds that determines maximal range which can be travelled using driving time. The Consumption Model will only affect the range when routeType is eco.
Exactly one budget (fuelBudgetInLiters, energyBudgetInkWh, timeBudgetInSec, or distanceBudgetInMeters) must be used. ,
Format: double ,
Required: False ,
}
number ,
distanceBudgetInMeters:
{
Description: Distance budget in meters that determines maximal range which can be travelled using driving distance. The Consumption Model will only affect the range when routeType is eco.
Exactly one budget (fuelBudgetInLiters, energyBudgetInkWh, timeBudgetInSec, or distanceBudgetInMeters) must be used. ,
Format: double ,
Required: False ,
}
number ,
departAt:
{
Description: The date and time of departure from the origin point formatted as a `dateTime` value as defined in [RFC 3339, section 5.6](https://www.rfc-editor.org/rfc/rfc3339#section-5.6), with an optional time zone offset. When a time zone offset is not specified, it will be assumed to be that of the origin point. * Default value: now * Other value: `dateTime` Examples: * 2023-12-19T16:39:57 * 2023-12-19T16:39:57-08:00 The `departAt` parameter cannot be used in conjunction with `arriveAt`. ,
Format: date-time ,
Required: False ,
}
string ,
routeType:
{
Description: The type of route requested. ,
Required: False ,
}
string ,
traffic:
{
Description: Possible values: * true - Do consider all available traffic information during routing * false - Ignore current traffic data during routing. Note that although the current traffic data is ignored during routing, the effect of historic traffic on effective road speeds is still incorporated. ,
Required: False ,
}
boolean ,
avoid:
{
Description: Specifies something that the route calculation should try to avoid when determining the route. Can be specified multiple times in one request, for example, '&avoid=motorways&avoid=tollRoads&avoid=ferries'. In Route Range requests, the value alreadyUsedRoads must not be used. ,
Required: False ,
}
array ,
travelMode:
{
Description: The mode of travel for the requested route. If not defined, default is 'car'. Note that the requested travelMode may not be available for the entire route. Where the requested travelMode is not available for a particular section, the travelMode element of the response for that section will be "other". Note that travel modes bus, motorcycle, taxi and van are BETA functionality. Full restriction data is not available in all areas. ,
Required: False ,
}
string ,
hilliness:
{
Description: Degree of hilliness for thrilling route. This parameter can only be used in conjunction with `routeType`=thrilling. ,
Required: False ,
}
string ,
windingness:
{
Description: Level of turns for thrilling route. This parameter can only be used in conjunction with `routeType`=thrilling. ,
Required: False ,
}
string ,
vehicleAxleWeight:
{
Description: Weight per axle of the vehicle in kg. A value of 0 means that weight restrictions per axle are not considered. ,
Required: False ,
}
integer ,
vehicleWidth:
{
Description: Width of the vehicle in meters. A value of 0 means that width restrictions are not considered. ,
Format: double ,
Required: False ,
}
number ,
vehicleHeight:
{
Description: Height of the vehicle in meters. A value of 0 means that height restrictions are not considered. ,
Format: double ,
Required: False ,
}
number ,
vehicleLength:
{
Description: Length of the vehicle in meters. A value of 0 means that length restrictions are not considered. ,
Format: double ,
Required: False ,
}
number ,
vehicleMaxSpeed:
{
Description: Maximum speed of the vehicle in km/hour. The max speed in the vehicle profile is used to check whether a vehicle is allowed on motorways. * A value of 0 means that an appropriate value for the vehicle will be determined and applied during route planning. * A non-zero value may be overridden during route planning. For example, the current traffic flow is 60 km/hour. If the vehicle maximum speed is set to 50 km/hour, the routing engine will consider 60 km/hour as this is the current situation. If the maximum speed of the vehicle is provided as 80 km/hour but the current traffic flow is 60 km/hour, then routing engine will again use 60 km/hour. ,
Required: False ,
}
integer ,
vehicleWeight:
{
Description: Weight of the vehicle in kilograms. * It is mandatory if any of the *Efficiency parameters are set. * It must be strictly positive when used in the context of the Consumption Model. Weight restrictions are considered. * If no detailed **Consumption Model** is specified and the value of **vehicleWeight** is non-zero, then weight restrictions are considered. * In all other cases, this parameter is ignored. Sensible Values : for **Combustion Model** : 1600, for **Electric Model** : 1900 ,
Required: False ,
}
integer ,
vehicleCommercial:
{
Description: Whether the vehicle is used for commercial purposes. Commercial vehicles may not be allowed to drive on some roads. ,
Required: False ,
}
boolean ,
vehicleLoadType:
{
Description: Types of cargo that may be classified as hazardous materials and restricted from some roads. Available vehicleLoadType values are US Hazmat classes 1 through 9, plus generic classifications for use in other countries/regions. Values beginning with USHazmat are for US routing while otherHazmat should be used for all other countries/regions. vehicleLoadType can be specified multiple times. This parameter is currently only considered for travelMode=truck. ,
Required: False ,
}
string ,
vehicleEngineType:
{
Description: Engine type of the vehicle. When a detailed Consumption Model is specified, it must be consistent with the value of **vehicleEngineType**. ,
Required: False ,
}
string ,
constantSpeedConsumptionInLitersPerHundredkm:
{
Description: Specifies the speed-dependent component of consumption. Provided as an unordered list of colon-delimited speed & consumption-rate pairs. The list defines points on a consumption curve. Consumption rates for speeds not in the list are found as follows: * by linear interpolation, if the given speed lies in between two speeds in the list * by linear extrapolation otherwise, assuming a constant (ΔConsumption/ΔSpeed) determined by the nearest two points in the list The list must contain between 1 and 25 points (inclusive), and may not contain duplicate points for the same speed. If it only contains a single point, then the consumption rate of that point is used without further processing. Consumption specified for the largest speed must be greater than or equal to that of the penultimate largest speed. This ensures that extrapolation does not lead to negative consumption rates. Similarly, consumption values specified for the two smallest speeds in the list cannot lead to a negative consumption rate for any smaller speed. The valid range for the consumption values(expressed in l/100km) is between 0.01 and 100000.0. Sensible Values : 50,6.3:130,11.5 **Note** : This parameter is required for **The Combustion Consumption Model**. ,
Required: False ,
}
string ,
currentFuelInLiters:
{
Description: Specifies the current supply of fuel in liters. Sensible Values : 55 ,
Format: double ,
Required: False ,
}
number ,
auxiliaryPowerInLitersPerHour:
{
Description: Specifies the amount of fuel consumed for sustaining auxiliary systems of the vehicle, in liters per hour. It can be used to specify consumption due to devices and systems such as AC systems, radio, heating, etc. Sensible Values : 0.2 ,
Format: double ,
Required: False ,
}
number ,
fuelEnergyDensityInMJoulesPerLiter:
{
Description: Specifies the amount of chemical energy stored in one liter of fuel in megajoules (MJ). It is used in conjunction with the ***Efficiency** parameters for conversions between saved or consumed energy and fuel. For example, energy density is 34.2 MJ/l for gasoline, and 35.8 MJ/l for Diesel fuel. This parameter is required if any ***Efficiency** parameter is set. Sensible Values : 34.2 ,
Format: double ,
Required: False ,
}
number ,
accelerationEfficiency:
{
Description: Specifies the efficiency of converting chemical energy stored in fuel to kinetic energy when the vehicle accelerates _(i.e. KineticEnergyGained/ChemicalEnergyConsumed). ChemicalEnergyConsumed_ is obtained by converting consumed fuel to chemical energy using **fuelEnergyDensityInMJoulesPerLiter**. Must be paired with **decelerationEfficiency**. The range of values allowed are 0.0 to 1/**decelerationEfficiency**. Sensible Values : for **Combustion Model** : 0.33, for **Electric Model** : 0.66 ,
Format: double ,
Required: False ,
}
number ,
decelerationEfficiency:
{
Description: Specifies the efficiency of converting kinetic energy to saved (not consumed) fuel when the vehicle decelerates _(i.e. ChemicalEnergySaved/KineticEnergyLost). ChemicalEnergySaved_ is obtained by converting saved (not consumed) fuel to energy using **fuelEnergyDensityInMJoulesPerLiter**. Must be paired with **accelerationEfficiency**. The range of values allowed are 0.0 to 1/**accelerationEfficiency**. Sensible Values : for **Combustion Model** : 0.83, for **Electric Model** : 0.91 ,
Format: double ,
Required: False ,
}
number ,
uphillEfficiency:
{
Description: Specifies the efficiency of converting chemical energy stored in fuel to potential energy when the vehicle gains elevation _(i.e. PotentialEnergyGained/ChemicalEnergyConsumed). ChemicalEnergyConsumed_ is obtained by converting consumed fuel to chemical energy using **fuelEnergyDensityInMJoulesPerLiter**. Must be paired with **downhillEfficiency**. The range of values allowed are 0.0 to 1/**downhillEfficiency**. Sensible Values : for **Combustion Model** : 0.27, for **Electric Model** : 0.74 ,
Format: double ,
Required: False ,
}
number ,
downhillEfficiency:
{
Description: Specifies the efficiency of converting potential energy to saved (not consumed) fuel when the vehicle loses elevation _(i.e. ChemicalEnergySaved/PotentialEnergyLost). ChemicalEnergySaved_ is obtained by converting saved (not consumed) fuel to energy using **fuelEnergyDensityInMJoulesPerLiter**. Must be paired with **uphillEfficiency**. The range of values allowed are 0.0 to 1/**uphillEfficiency**. Sensible Values : for **Combustion Model** : 0.51, for **Electric Model** : 0.73 ,
Format: double ,
Required: False ,
}
number ,
constantSpeedConsumptionInkWhPerHundredkm:
{
Description: Specifies the speed-dependent component of consumption. Provided as an unordered list of speed/consumption-rate pairs. The list defines points on a consumption curve. Consumption rates for speeds not in the list are found as follows: * by linear interpolation, if the given speed lies in between two speeds in the list * by linear extrapolation otherwise, assuming a constant (ΔConsumption/ΔSpeed) determined by the nearest two points in the list The list must contain between 1 and 25 points (inclusive), and may not contain duplicate points for the same speed. If it only contains a single point, then the consumption rate of that point is used without further processing. Consumption specified for the largest speed must be greater than or equal to that of the penultimate largest speed. This ensures that extrapolation does not lead to negative consumption rates. Similarly, consumption values specified for the two smallest speeds in the list cannot lead to a negative consumption rate for any smaller speed. The valid range for the consumption values(expressed in kWh/100km) is between 0.01 and 100000.0. Sensible Values : 50,8.2:130,21.3 This parameter is required for **Electric consumption model**. ,
Required: False ,
}
string ,
currentChargeInkWh:
{
Description: Specifies the current electric energy supply in kilowatt hours (kWh). This parameter co-exists with **maxChargeInkWh** parameter. The range of values allowed are 0.0 to **maxChargeInkWh**. Sensible Values : 43 ,
Format: double ,
Required: False ,
}
number ,
maxChargeInkWh:
{
Description: Specifies the maximum electric energy supply in kilowatt hours (kWh) that may be stored in the vehicle's battery. This parameter co-exists with **currentChargeInkWh** parameter. Minimum value has to be greater than or equal to **currentChargeInkWh**. Sensible Values : 85 ,
Format: double ,
Required: False ,
}
number ,
auxiliaryPowerInkW:
{
Description: Specifies the amount of power consumed for sustaining auxiliary systems, in kilowatts (kW). It can be used to specify consumption due to devices and systems such as AC systems, radio, heating, etc. Sensible Values : 1.7 ,
Format: double ,
Required: False ,
}
number ,
}

⚐ Response (200)

{
formatVersion:
{
Description: Format Version property ,
Required: False ,
}
string ,
reachableRange:
{
Description: Reachable Range ,
Required: False ,
}
{
center:
{
Description: Center point of the reachable range ,
Required: False ,
}
{
latitude:
{
Description: Latitude property ,
Format: double ,
Required: False ,
}
number ,
longitude:
{
Description: Longitude property ,
Format: double ,
Required: False ,
}
number ,
}
,
boundary:
{
Description: Polygon boundary of the reachable range represented as a list of points. ,
Required: False ,
}
[
{
latitude:
{
Description: Latitude property ,
Format: double ,
Required: False ,
}
number ,
longitude:
{
Description: Longitude property ,
Format: double ,
Required: False ,
}
number ,
}
,
]
,
}
,
report:
{
Description: Reports the effective settings used in the current call. ,
Required: False ,
}
{
effectiveSettings:
{
Description: Effective parameters or data used when calling this Route API. ,
Required: False ,
}
[
{
key:
{
Description: Name of the parameter used. ,
Required: False ,
}
string ,
value:
{
Description: Value of the parameter used. ,
Required: False ,
}
string ,
}
,
]
,
}
,
}

⚐ Response (default)

{
error:
{
Description: The error object. ,
Required: False ,
}
{
code:
{
Description: The error code. ,
Required: False ,
}
string ,
message:
{
Description: The error message. ,
Required: False ,
}
string ,
target:
{
Description: The error target. ,
Required: False ,
}
string ,
details:
{
Description: The error details. ,
Required: False ,
}
[
{
code:
{
Description: The error code. ,
Required: False ,
}
string ,
message:
{
Description: The error message. ,
Required: False ,
}
string ,
target:
{
Description: The error target. ,
Required: False ,
}
string ,
details:
{
Description: The error details. ,
Required: False ,
}
[
string ,
]
,
additionalInfo:
{
Description: The error additional info. ,
Required: False ,
}
[
{
type:
{
Description: The additional info type. ,
Required: False ,
}
string ,
info:
{
Description: The additional info. ,
Required: False ,
}
object ,
}
,
]
,
}
,
]
,
additionalInfo:
{
Description: The error additional info. ,
Required: False ,
}
[
{
type:
{
Description: The additional info type. ,
Required: False ,
}
string ,
info:
{
Description: The additional info. ,
Required: False ,
}
object ,
}
,
]
,
}
,
}
Route_PostRouteDirectionsBatch (updated)
Description :  > [!NOTE] > > **Azure Maps Route v1 service retirement** > > The Azure Maps [Route v1](/rest/api/maps/route?view=rest-maps-1.0) service is now deprecated and will be retired on 3/31/28. To avoid service disruptions, all calls to Route v1 service will need to be updated to use [Route v2025-01-01](/rest/api/maps/route) service by 3/31/28. For more information, see [Migrate Azure Maps Route 1.0 APIs](/azure/azure-maps/migrate-route-v1-api). The `Post Route Directions Batch` API is an HTTP `POST` request that sends batches of queries to the [Get Route Directions](/rest/api/maps/route/get-route-directions) API using a single asynchronous request. You can call `Route Directions Batch` API to run either asynchronously (async) or synchronously (sync). The async API allows caller to batch up to **700** queries and sync API up to **100** queries. To call the `Post Route Directions Batch` API in a synchronous request, see [Post Route Directions Batch Sync](/rest/api/maps/route/post-route-directions-batch-sync). ### Submit Asynchronous Batch Request The Asynchronous API is appropriate for processing big volumes of relatively complex route requests - It allows the retrieval of results in a separate call (multiple downloads are possible). - The asynchronous API is optimized for reliability and is not expected to run into a timeout. - The number of batch items is limited to **700** for this API. When you make a request by using async request, by default the service returns a 202 response code along a redirect URL in the Location field of the response header. This URL should be checked periodically until the response data or error information is available. The asynchronous responses are stored for **24** hours. The redirect URL returns a 404 response if used after the expiration period. Please note that asynchronous batch request is a long-running operation. Here's a typical sequence of operations: 1. Client sends a Route Directions Batch `POST` request to Azure Maps. ``` POST https://atlas.microsoft.com/route/directions/batch/json?api-version=1.0&subscription-key={subscription-key} ``` 2. The server will respond with one of the following: > HTTP `202 Accepted` - Batch request has been accepted. > HTTP `Error` - There was an error processing your Batch request. This could either be a `400 Bad Request` or any other `Error` status code. 3. If the batch request was accepted successfully, the `Location` header in the response contains the URL to download the results of the batch request. This status URI looks like following: ``` GET https://atlas.microsoft.com/route/directions/batch/{batch-id}?api-version=1.0&subscription-key={subscription-key} ``` 4. Client issues a `GET` request on the _download URL_ obtained in Step 3 to download the batch results. ### POST Body for Batch Request To send the _route directions_ queries you will use a `POST` request where the request body will contain the `batchItems` array in `json` format and the `Content-Type` header will be set to `application/json`. Here's a sample request body containing 3 _route directions_ queries: ```json { "batchItems": [ { "query": "?query=47.620659,-122.348934:47.610101,-122.342015&travelMode=bicycle&routeType=eco&traffic=false" }, { "query": "?query=40.759856,-73.985108:40.771136,-73.973506&travelMode=pedestrian&routeType=shortest" }, { "query": "?query=48.923159,-122.557362:32.621279,-116.840362" } ] } ``` A _route directions_ query in a batch is just a partial URL _without_ the protocol, base URL, path, api-version and subscription-key. It can accept any of the supported _route directions_ [URI parameters](https://docs.microsoft.com/rest/api/maps/route/getroutedirections#uri-parameters). The string values in the _route directions_ query must be properly escaped (e.g. " character should be escaped with \\ ) and it should also be properly URL-encoded. The async API allows caller to batch up to **700** queries and sync API up to **100** queries, and the batch should contain at least **1** query. ### Download Asynchronous Batch Results To download the async batch results you will issue a `GET` request to the batch download endpoint. This _download URL_ can be obtained from the `Location` header of a successful `POST` batch request and looks like the following: ``` https://atlas.microsoft.com/route/directions/batch/{batch-id}?api-version=1.0&subscription-key={subscription-key} ``` Here's the typical sequence of operations for downloading the batch results: 1. Client sends a `GET` request using the _download URL_. 2. The server will respond with one of the following: > HTTP `202 Accepted` - Batch request was accepted but is still being processed. Please try again in some time. > HTTP `200 OK` - Batch request successfully processed. The response body contains all the batch results. ### Batch Response Model The returned data content is similar for async and sync requests. When downloading the results of an async batch request, if the batch has finished processing, the response body contains the batch response. This batch response contains a `summary` component that indicates the `totalRequests` that were part of the original batch request and `successfulRequests`i.e. queries which were executed successfully. The batch response also includes a `batchItems` array which contains a response for each and every query in the batch request. The `batchItems` will contain the results in the exact same order the original queries were sent in the batch request. Each item in `batchItems` contains `statusCode` and `response` fields. Each `response` in `batchItems` is of one of the following types: - [`RouteDirections`](https://docs.microsoft.com/rest/api/maps/route/getroutedirections#routedirections) - If the query completed successfully. - `Error` - If the query failed. The response will contain a `code` and a `message` in this case. Here's a sample Batch Response with 1 _successful_ and 1 _failed_ result: ```json { "summary": { "successfulRequests": 1, "totalRequests": 2 }, "batchItems": [ { "statusCode": 200, "response": { "routes": [ { "summary": { "lengthInMeters": 1758, "travelTimeInSeconds": 387, "trafficDelayInSeconds": 0, "departureTime": "2018-07-17T00:49:56+00:00", "arrivalTime": "2018-07-17T00:56:22+00:00" }, "legs": [ { "summary": { "lengthInMeters": 1758, "travelTimeInSeconds": 387, "trafficDelayInSeconds": 0, "departureTime": "2018-07-17T00:49:56+00:00", "arrivalTime": "2018-07-17T00:56:22+00:00" }, "points": [ { "latitude": 47.62094, "longitude": -122.34892 }, { "latitude": 47.62094, "longitude": -122.3485 }, { "latitude": 47.62095, "longitude": -122.3476 } ] } ], "sections": [ { "startPointIndex": 0, "endPointIndex": 40, "sectionType": "TRAVEL_MODE", "travelMode": "bicycle" } ] } ] } }, { "statusCode": 400, "response": { "error": { "code": "400 BadRequest", "message": "Bad request: one or more parameters were incorrectly specified or are mutually exclusive." } } } ] } ```
Reference :  Link ¶

⚶ Changes

{
  "#id": "Route_PostRouteDirectionsBatch",
  "Description": {
    "new": "\n\n> [!NOTE]\n>\n> **Azure Maps Route v1 service retirement**\n>\n> The Azure Maps [Route v1](/rest/api/maps/route?view=rest-maps-1.0) service is now deprecated and will be retired on 3/31/28. To avoid service disruptions, all calls to Route v1 service will need to be updated to use [Route v2025-01-01](/rest/api/maps/route) service by 3/31/28. For more information, see [Migrate Azure Maps Route 1.0 APIs](/azure/azure-maps/migrate-route-v1-api).\n\nThe `Post Route Directions Batch` API is an HTTP `POST` request that sends batches of queries to the [Get Route Directions](/rest/api/maps/route/get-route-directions) API using a single asynchronous request. You can call `Route Directions Batch` API to run either asynchronously (async) or synchronously (sync). The async API allows caller to batch up to **700** queries and sync API up to **100** queries. To call the `Post Route Directions Batch` API in a synchronous request, see [Post Route Directions Batch Sync](/rest/api/maps/route/post-route-directions-batch-sync).\n\n### Submit Asynchronous Batch Request\nThe Asynchronous API is appropriate for processing big volumes of relatively complex route requests\n- It allows the retrieval of results in a separate call (multiple downloads are possible).\n- The asynchronous API is optimized for reliability and is not expected to run into a timeout.\n- The number of batch items is limited to **700** for this API.\n\nWhen you make a request by using async request, by default the service returns a 202 response code along a redirect URL in the Location field of the response header. This URL should be checked periodically until the response data or error information is available.\nThe asynchronous responses are stored for **24** hours. The redirect URL returns a 404 response if used after the expiration period.\n\nPlease note that asynchronous batch request is a long-running operation. Here's a typical sequence of operations:\n1. Client sends a Route Directions Batch `POST` request to Azure Maps.\n```\nPOST https://atlas.microsoft.com/route/directions/batch/json?api-version=1.0&subscription-key={subscription-key}\n```\n2. The server will respond with one of the following:\n\n    > HTTP `202 Accepted` - Batch request has been accepted.\n\n    > HTTP `Error` - There was an error processing your Batch request. This could either be a `400 Bad Request` or any other `Error` status code.\n\n3. If the batch request was accepted successfully, the `Location` header in the response contains the URL to download the results of the batch request.\n    This status URI looks like following:\n```\nGET https://atlas.microsoft.com/route/directions/batch/{batch-id}?api-version=1.0&subscription-key={subscription-key} \n```\n4. Client issues a `GET` request on the _download URL_ obtained in Step 3 to download the batch results.\n\n### POST Body for Batch Request\nTo send the _route directions_ queries you will use a `POST` request where the request body will contain the `batchItems` array in `json` format and the `Content-Type` header will be set to `application/json`. Here's a sample request body containing 3 _route directions_ queries:\n\n\n```json\n{\n    \"batchItems\": [\n        { \"query\": \"?query=47.620659,-122.348934:47.610101,-122.342015&travelMode=bicycle&routeType=eco&traffic=false\" },\n        { \"query\": \"?query=40.759856,-73.985108:40.771136,-73.973506&travelMode=pedestrian&routeType=shortest\" },\n        { \"query\": \"?query=48.923159,-122.557362:32.621279,-116.840362\" }\n    ]\n}\n```\n\nA _route directions_ query in a batch is just a partial URL _without_ the protocol, base URL, path, api-version and subscription-key. It can accept any of the supported _route directions_ [URI parameters](https://docs.microsoft.com/rest/api/maps/route/getroutedirections#uri-parameters). The string values in the _route directions_ query must be properly escaped (e.g. \" character should be escaped with \\\\ ) and it should also be properly URL-encoded.\n\n\nThe async API allows caller to batch up to **700** queries and sync API up to **100** queries, and the batch should contain at least **1** query.\n\n\n### Download Asynchronous Batch Results\nTo download the async batch results you will issue a `GET` request to the batch download endpoint. This _download URL_ can be obtained from the `Location` header of a successful `POST` batch request and looks like the following:\n\n```\nhttps://atlas.microsoft.com/route/directions/batch/{batch-id}?api-version=1.0&subscription-key={subscription-key}\n```\nHere's the typical sequence of operations for downloading the batch results:\n1. Client sends a `GET` request using the _download URL_.\n2. The server will respond with one of the following:\n    \n    > HTTP `202 Accepted` - Batch request was accepted but is still being processed. Please try again in some time.\n\n    > HTTP `200 OK` - Batch request successfully processed. The response body contains all the batch results.\n\n\n\n### Batch Response Model\nThe returned data content is similar for async and sync requests. When downloading the results of an async batch request, if the batch has finished processing, the response body contains the batch response. This batch response contains a `summary` component that indicates the `totalRequests` that were part of the original batch request and `successfulRequests`i.e. queries which were executed successfully. The batch response also includes a `batchItems` array which contains a response for each and every query in the batch request. The `batchItems` will contain the results in the exact same order the original queries were sent in the batch request. Each item in `batchItems` contains `statusCode` and `response` fields. Each `response` in `batchItems` is of one of the following types:\n\n  - [`RouteDirections`](https://docs.microsoft.com/rest/api/maps/route/getroutedirections#routedirections) - If the query completed successfully.\n\n  - `Error` - If the query failed. The response will contain a `code` and a `message` in this case.\n\n\nHere's a sample Batch Response with 1 _successful_ and 1 _failed_ result:\n\n\n```json\n{\n    \"summary\": {\n        \"successfulRequests\": 1,\n        \"totalRequests\": 2\n    },\n    \"batchItems\": [\n        {\n            \"statusCode\": 200,\n            \"response\": {\n                \"routes\": [\n                    {\n                        \"summary\": {\n                            \"lengthInMeters\": 1758,\n                            \"travelTimeInSeconds\": 387,\n                            \"trafficDelayInSeconds\": 0,\n                            \"departureTime\": \"2018-07-17T00:49:56+00:00\",\n                            \"arrivalTime\": \"2018-07-17T00:56:22+00:00\"\n                        },\n                        \"legs\": [\n                            {\n                                \"summary\": {\n                                    \"lengthInMeters\": 1758,\n                                    \"travelTimeInSeconds\": 387,\n                                    \"trafficDelayInSeconds\": 0,\n                                    \"departureTime\": \"2018-07-17T00:49:56+00:00\",\n                                    \"arrivalTime\": \"2018-07-17T00:56:22+00:00\"\n                                },\n                                \"points\": [\n                                    {\n                                        \"latitude\": 47.62094,\n                                        \"longitude\": -122.34892\n                                    },\n                                    {\n                                        \"latitude\": 47.62094,\n                                        \"longitude\": -122.3485\n                                    },\n                                    {\n                                        \"latitude\": 47.62095,\n                                        \"longitude\": -122.3476\n                                    }\n                                ]\n                            }\n                        ],\n                        \"sections\": [\n                            {\n                                \"startPointIndex\": 0,\n                                \"endPointIndex\": 40,\n                                \"sectionType\": \"TRAVEL_MODE\",\n                                \"travelMode\": \"bicycle\"\n                            }\n                        ]\n                    }\n                ]\n            }\n        },\n        {\n            \"statusCode\": 400,\n            \"response\":\n            {\n                \"error\":\n                {\n                    \"code\": \"400 BadRequest\",\n                    \"message\": \"Bad request: one or more parameters were incorrectly specified or are mutually exclusive.\"\n                }\n            }\n        }\n    ]\n}\n```",
    "old": "\n\nThe `Post Route Directions Batch` API is an HTTP `POST` request that sends batches of queries to the [Get Route Directions](/rest/api/maps/route/get-route-directions) API using a single asynchronous request. You can call `Route Directions Batch` API to run either asynchronously (async) or synchronously (sync). The async API allows caller to batch up to **700** queries and sync API up to **100** queries. To call the `Post Route Directions Batch` API in a synchronous request, see [Post Route Directions Batch Sync](/rest/api/maps/route/post-route-directions-batch-sync).\n\n### Submit Asynchronous Batch Request\nThe Asynchronous API is appropriate for processing big volumes of relatively complex route requests\n- It allows the retrieval of results in a separate call (multiple downloads are possible).\n- The asynchronous API is optimized for reliability and is not expected to run into a timeout.\n- The number of batch items is limited to **700** for this API.\n\nWhen you make a request by using async request, by default the service returns a 202 response code along a redirect URL in the Location field of the response header. This URL should be checked periodically until the response data or error information is available.\nThe asynchronous responses are stored for **24** hours. The redirect URL returns a 404 response if used after the expiration period.\n\nPlease note that asynchronous batch request is a long-running operation. Here's a typical sequence of operations:\n1. Client sends a Route Directions Batch `POST` request to Azure Maps.\n```\nPOST https://atlas.microsoft.com/route/directions/batch/json?api-version=1.0&subscription-key={subscription-key}\n```\n2. The server will respond with one of the following:\n\n    > HTTP `202 Accepted` - Batch request has been accepted.\n\n    > HTTP `Error` - There was an error processing your Batch request. This could either be a `400 Bad Request` or any other `Error` status code.\n\n3. If the batch request was accepted successfully, the `Location` header in the response contains the URL to download the results of the batch request.\n    This status URI looks like following:\n```\nGET https://atlas.microsoft.com/route/directions/batch/{batch-id}?api-version=1.0&subscription-key={subscription-key} \n```\n4. Client issues a `GET` request on the _download URL_ obtained in Step 3 to download the batch results.\n\n### POST Body for Batch Request\nTo send the _route directions_ queries you will use a `POST` request where the request body will contain the `batchItems` array in `json` format and the `Content-Type` header will be set to `application/json`. Here's a sample request body containing 3 _route directions_ queries:\n\n\n```json\n{\n    \"batchItems\": [\n        { \"query\": \"?query=47.620659,-122.348934:47.610101,-122.342015&travelMode=bicycle&routeType=eco&traffic=false\" },\n        { \"query\": \"?query=40.759856,-73.985108:40.771136,-73.973506&travelMode=pedestrian&routeType=shortest\" },\n        { \"query\": \"?query=48.923159,-122.557362:32.621279,-116.840362\" }\n    ]\n}\n```\n\nA _route directions_ query in a batch is just a partial URL _without_ the protocol, base URL, path, api-version and subscription-key. It can accept any of the supported _route directions_ [URI parameters](https://docs.microsoft.com/rest/api/maps/route/getroutedirections#uri-parameters). The string values in the _route directions_ query must be properly escaped (e.g. \" character should be escaped with \\\\ ) and it should also be properly URL-encoded.\n\n\nThe async API allows caller to batch up to **700** queries and sync API up to **100** queries, and the batch should contain at least **1** query.\n\n\n### Download Asynchronous Batch Results\nTo download the async batch results you will issue a `GET` request to the batch download endpoint. This _download URL_ can be obtained from the `Location` header of a successful `POST` batch request and looks like the following:\n\n```\nhttps://atlas.microsoft.com/route/directions/batch/{batch-id}?api-version=1.0&subscription-key={subscription-key}\n```\nHere's the typical sequence of operations for downloading the batch results:\n1. Client sends a `GET` request using the _download URL_.\n2. The server will respond with one of the following:\n    \n    > HTTP `202 Accepted` - Batch request was accepted but is still being processed. Please try again in some time.\n\n    > HTTP `200 OK` - Batch request successfully processed. The response body contains all the batch results.\n\n\n\n### Batch Response Model\nThe returned data content is similar for async and sync requests. When downloading the results of an async batch request, if the batch has finished processing, the response body contains the batch response. This batch response contains a `summary` component that indicates the `totalRequests` that were part of the original batch request and `successfulRequests`i.e. queries which were executed successfully. The batch response also includes a `batchItems` array which contains a response for each and every query in the batch request. The `batchItems` will contain the results in the exact same order the original queries were sent in the batch request. Each item in `batchItems` contains `statusCode` and `response` fields. Each `response` in `batchItems` is of one of the following types:\n\n  - [`RouteDirections`](https://docs.microsoft.com/rest/api/maps/route/getroutedirections#routedirections) - If the query completed successfully.\n\n  - `Error` - If the query failed. The response will contain a `code` and a `message` in this case.\n\n\nHere's a sample Batch Response with 1 _successful_ and 1 _failed_ result:\n\n\n```json\n{\n    \"summary\": {\n        \"successfulRequests\": 1,\n        \"totalRequests\": 2\n    },\n    \"batchItems\": [\n        {\n            \"statusCode\": 200,\n            \"response\": {\n                \"routes\": [\n                    {\n                        \"summary\": {\n                            \"lengthInMeters\": 1758,\n                            \"travelTimeInSeconds\": 387,\n                            \"trafficDelayInSeconds\": 0,\n                            \"departureTime\": \"2018-07-17T00:49:56+00:00\",\n                            \"arrivalTime\": \"2018-07-17T00:56:22+00:00\"\n                        },\n                        \"legs\": [\n                            {\n                                \"summary\": {\n                                    \"lengthInMeters\": 1758,\n                                    \"travelTimeInSeconds\": 387,\n                                    \"trafficDelayInSeconds\": 0,\n                                    \"departureTime\": \"2018-07-17T00:49:56+00:00\",\n                                    \"arrivalTime\": \"2018-07-17T00:56:22+00:00\"\n                                },\n                                \"points\": [\n                                    {\n                                        \"latitude\": 47.62094,\n                                        \"longitude\": -122.34892\n                                    },\n                                    {\n                                        \"latitude\": 47.62094,\n                                        \"longitude\": -122.3485\n                                    },\n                                    {\n                                        \"latitude\": 47.62095,\n                                        \"longitude\": -122.3476\n                                    }\n                                ]\n                            }\n                        ],\n                        \"sections\": [\n                            {\n                                \"startPointIndex\": 0,\n                                \"endPointIndex\": 40,\n                                \"sectionType\": \"TRAVEL_MODE\",\n                                \"travelMode\": \"bicycle\"\n                            }\n                        ]\n                    }\n                ]\n            }\n        },\n        {\n            \"statusCode\": 400,\n            \"response\":\n            {\n                \"error\":\n                {\n                    \"code\": \"400 BadRequest\",\n                    \"message\": \"Bad request: one or more parameters were incorrectly specified or are mutually exclusive.\"\n                }\n            }\n        }\n    ]\n}\n```"
  }
}

⚼ Request

POST:  /route/directions/batch/{format}
{
x-ms-client-id:
{
Description: Specifies which account is intended for usage in conjunction with the Microsoft Entra ID security model. It represents a unique ID for the Azure Maps account and can be retrieved from the Azure Maps management plane Account API. To use Microsoft Entra ID security in Azure Maps see the following [articles](https://aka.ms/amauthdetails) for guidance. ,
Required: False ,
}
string ,
api-version:
{
Description: Version number of Azure Maps API. ,
Required: True ,
}
string ,
format:
{
Description: Desired format of the response. Only `json` format is supported. ,
Required: True ,
}
string ,
routeDirectionsBatchQueries:
{
Description: The list of route directions queries/requests to process. The list can contain a max of 700 queries for async and 100 queries for sync version and must contain at least 1 query. ,
Required: True ,
}
{
batchItems:
{
Description: The list of queries to process. ,
Required: False ,
}
[
{
query:
{
Description: This parameter contains a query string used to perform an unstructured geocoding operation. The query string will be passed verbatim to the search API for processing. ,
Required: False ,
}
string ,
}
,
]
,
}
,
}

⚐ Response (200)

{
batchItems:
{
Description: Array containing the batch results. ,
Required: False ,
}
[
{
response:
{
Description: The result of the query. RouteDirections if the query completed successfully, ErrorResponse otherwise. ,
Required: False ,
}
object ,
}
,
]
,
}

⚐ Response (202)

{
location:
{
Description: New URL to check for the results of the long-running operation. ,
}
string ,
}

⚐ Response (default)

{
error:
{
Description: The error object. ,
Required: False ,
}
{
code:
{
Description: The error code. ,
Required: False ,
}
string ,
message:
{
Description: The error message. ,
Required: False ,
}
string ,
target:
{
Description: The error target. ,
Required: False ,
}
string ,
details:
{
Description: The error details. ,
Required: False ,
}
[
{
code:
{
Description: The error code. ,
Required: False ,
}
string ,
message:
{
Description: The error message. ,
Required: False ,
}
string ,
target:
{
Description: The error target. ,
Required: False ,
}
string ,
details:
{
Description: The error details. ,
Required: False ,
}
[
string ,
]
,
additionalInfo:
{
Description: The error additional info. ,
Required: False ,
}
[
{
type:
{
Description: The additional info type. ,
Required: False ,
}
string ,
info:
{
Description: The additional info. ,
Required: False ,
}
object ,
}
,
]
,
}
,
]
,
additionalInfo:
{
Description: The error additional info. ,
Required: False ,
}
[
{
type:
{
Description: The additional info type. ,
Required: False ,
}
string ,
info:
{
Description: The additional info. ,
Required: False ,
}
object ,
}
,
]
,
}
,
}
Route_GetRouteDirectionsBatch (updated)
Description :  > [!NOTE] > > **Azure Maps Route v1 service retirement** > > The Azure Maps [Route v1](/rest/api/maps/route?view=rest-maps-1.0) service is now deprecated and will be retired on 3/31/28. To avoid service disruptions, all calls to Route v1 service will need to be updated to use [Route v2025-01-01](/rest/api/maps/route) service by 3/31/28. For more information, see [Migrate Azure Maps Route 1.0 APIs](/azure/azure-maps/migrate-route-v1-api). The `Get Route Directions Batch` API is an HTTP `GET` request that sends batches of queries to the [Get Route Directions](/rest/api/maps/route/get-route-directions) API using a single request. You can call `Get Route Directions Batch` API to run either asynchronously (async) or synchronously (sync). The async API allows caller to batch up to **700** queries and sync API up to **100** queries. ### Download Asynchronous Batch Results To download the async batch results you will issue a `GET` request to the batch download endpoint. This _download URL_ can be obtained from the `Location` header of a successful `POST` batch request and looks like the following: ``` https://atlas.microsoft.com/route/directions/batch/{batch-id}?api-version=1.0&subscription-key={subscription-key} ``` Here's the typical sequence of operations for downloading the batch results: 1. Client sends a `GET` request using the _download URL_. 2. The server will respond with one of the following: > HTTP `202 Accepted` - Batch request was accepted but is still being processed. Please try again in some time. > HTTP `200 OK` - Batch request successfully processed. The response body contains all the batch results. ### Batch Response Model The returned data content is similar for async and sync requests. When downloading the results of an async batch request, if the batch has finished processing, the response body contains the batch response. This batch response contains a `summary` component that indicates the `totalRequests` that were part of the original batch request and `successfulRequests`i.e. queries which were executed successfully. The batch response also includes a `batchItems` array which contains a response for each and every query in the batch request. The `batchItems` will contain the results in the exact same order the original queries were sent in the batch request. Each item in `batchItems` contains `statusCode` and `response` fields. Each `response` in `batchItems` is of one of the following types: - [`RouteDirections`](https://docs.microsoft.com/rest/api/maps/route/getroutedirections#routedirections) - If the query completed successfully. - `Error` - If the query failed. The response will contain a `code` and a `message` in this case. Here's a sample Batch Response with 1 _successful_ and 1 _failed_ result: ```json { "summary": { "successfulRequests": 1, "totalRequests": 2 }, "batchItems": [ { "statusCode": 200, "response": { "routes": [ { "summary": { "lengthInMeters": 1758, "travelTimeInSeconds": 387, "trafficDelayInSeconds": 0, "departureTime": "2018-07-17T00:49:56+00:00", "arrivalTime": "2018-07-17T00:56:22+00:00" }, "legs": [ { "summary": { "lengthInMeters": 1758, "travelTimeInSeconds": 387, "trafficDelayInSeconds": 0, "departureTime": "2018-07-17T00:49:56+00:00", "arrivalTime": "2018-07-17T00:56:22+00:00" }, "points": [ { "latitude": 47.62094, "longitude": -122.34892 }, { "latitude": 47.62094, "longitude": -122.3485 }, { "latitude": 47.62095, "longitude": -122.3476 } ] } ], "sections": [ { "startPointIndex": 0, "endPointIndex": 40, "sectionType": "TRAVEL_MODE", "travelMode": "bicycle" } ] } ] } }, { "statusCode": 400, "response": { "error": { "code": "400 BadRequest", "message": "Bad request: one or more parameters were incorrectly specified or are mutually exclusive." } } } ] } ```
Reference :  Link ¶

⚶ Changes

{
  "#id": "Route_GetRouteDirectionsBatch",
  "Description": {
    "new": "\n\n> [!NOTE]\n>\n> **Azure Maps Route v1 service retirement**\n>\n> The Azure Maps [Route v1](/rest/api/maps/route?view=rest-maps-1.0) service is now deprecated and will be retired on 3/31/28. To avoid service disruptions, all calls to Route v1 service will need to be updated to use [Route v2025-01-01](/rest/api/maps/route) service by 3/31/28. For more information, see [Migrate Azure Maps Route 1.0 APIs](/azure/azure-maps/migrate-route-v1-api).\n\nThe `Get Route Directions Batch` API is an HTTP `GET` request that sends batches of queries to the [Get Route Directions](/rest/api/maps/route/get-route-directions) API using a single request. You can call `Get Route Directions Batch` API to run either asynchronously (async) or synchronously (sync). The async API allows caller to batch up to **700** queries and sync API up to **100** queries.\n\n### Download Asynchronous Batch Results\nTo download the async batch results you will issue a `GET` request to the batch download endpoint. This _download URL_ can be obtained from the `Location` header of a successful `POST` batch request and looks like the following:\n\n```\nhttps://atlas.microsoft.com/route/directions/batch/{batch-id}?api-version=1.0&subscription-key={subscription-key}\n```\nHere's the typical sequence of operations for downloading the batch results:\n1. Client sends a `GET` request using the _download URL_.\n2. The server will respond with one of the following:\n    \n    > HTTP `202 Accepted` - Batch request was accepted but is still being processed. Please try again in some time.\n\n    > HTTP `200 OK` - Batch request successfully processed. The response body contains all the batch results.\n\n\n\n### Batch Response Model\nThe returned data content is similar for async and sync requests. When downloading the results of an async batch request, if the batch has finished processing, the response body contains the batch response. This batch response contains a `summary` component that indicates the `totalRequests` that were part of the original batch request and `successfulRequests`i.e. queries which were executed successfully. The batch response also includes a `batchItems` array which contains a response for each and every query in the batch request. The `batchItems` will contain the results in the exact same order the original queries were sent in the batch request. Each item in `batchItems` contains `statusCode` and `response` fields. Each `response` in `batchItems` is of one of the following types:\n\n  - [`RouteDirections`](https://docs.microsoft.com/rest/api/maps/route/getroutedirections#routedirections) - If the query completed successfully.\n\n  - `Error` - If the query failed. The response will contain a `code` and a `message` in this case.\n\n\nHere's a sample Batch Response with 1 _successful_ and 1 _failed_ result:\n\n\n```json\n{\n    \"summary\": {\n        \"successfulRequests\": 1,\n        \"totalRequests\": 2\n    },\n    \"batchItems\": [\n        {\n            \"statusCode\": 200,\n            \"response\": {\n                \"routes\": [\n                    {\n                        \"summary\": {\n                            \"lengthInMeters\": 1758,\n                            \"travelTimeInSeconds\": 387,\n                            \"trafficDelayInSeconds\": 0,\n                            \"departureTime\": \"2018-07-17T00:49:56+00:00\",\n                            \"arrivalTime\": \"2018-07-17T00:56:22+00:00\"\n                        },\n                        \"legs\": [\n                            {\n                                \"summary\": {\n                                    \"lengthInMeters\": 1758,\n                                    \"travelTimeInSeconds\": 387,\n                                    \"trafficDelayInSeconds\": 0,\n                                    \"departureTime\": \"2018-07-17T00:49:56+00:00\",\n                                    \"arrivalTime\": \"2018-07-17T00:56:22+00:00\"\n                                },\n                                \"points\": [\n                                    {\n                                        \"latitude\": 47.62094,\n                                        \"longitude\": -122.34892\n                                    },\n                                    {\n                                        \"latitude\": 47.62094,\n                                        \"longitude\": -122.3485\n                                    },\n                                    {\n                                        \"latitude\": 47.62095,\n                                        \"longitude\": -122.3476\n                                    }\n                                ]\n                            }\n                        ],\n                        \"sections\": [\n                            {\n                                \"startPointIndex\": 0,\n                                \"endPointIndex\": 40,\n                                \"sectionType\": \"TRAVEL_MODE\",\n                                \"travelMode\": \"bicycle\"\n                            }\n                        ]\n                    }\n                ]\n            }\n        },\n        {\n            \"statusCode\": 400,\n            \"response\":\n            {\n                \"error\":\n                {\n                    \"code\": \"400 BadRequest\",\n                    \"message\": \"Bad request: one or more parameters were incorrectly specified or are mutually exclusive.\"\n                }\n            }\n        }\n    ]\n}\n```",
    "old": "\n\nThe `Get Route Directions Batch` API is an HTTP `GET` request that sends batches of queries to the [Get Route Directions](/rest/api/maps/route/get-route-directions) API using a single request. You can call `Get Route Directions Batch` API to run either asynchronously (async) or synchronously (sync). The async API allows caller to batch up to **700** queries and sync API up to **100** queries.\n\n### Download Asynchronous Batch Results\nTo download the async batch results you will issue a `GET` request to the batch download endpoint. This _download URL_ can be obtained from the `Location` header of a successful `POST` batch request and looks like the following:\n\n```\nhttps://atlas.microsoft.com/route/directions/batch/{batch-id}?api-version=1.0&subscription-key={subscription-key}\n```\nHere's the typical sequence of operations for downloading the batch results:\n1. Client sends a `GET` request using the _download URL_.\n2. The server will respond with one of the following:\n    \n    > HTTP `202 Accepted` - Batch request was accepted but is still being processed. Please try again in some time.\n\n    > HTTP `200 OK` - Batch request successfully processed. The response body contains all the batch results.\n\n\n\n### Batch Response Model\nThe returned data content is similar for async and sync requests. When downloading the results of an async batch request, if the batch has finished processing, the response body contains the batch response. This batch response contains a `summary` component that indicates the `totalRequests` that were part of the original batch request and `successfulRequests`i.e. queries which were executed successfully. The batch response also includes a `batchItems` array which contains a response for each and every query in the batch request. The `batchItems` will contain the results in the exact same order the original queries were sent in the batch request. Each item in `batchItems` contains `statusCode` and `response` fields. Each `response` in `batchItems` is of one of the following types:\n\n  - [`RouteDirections`](https://docs.microsoft.com/rest/api/maps/route/getroutedirections#routedirections) - If the query completed successfully.\n\n  - `Error` - If the query failed. The response will contain a `code` and a `message` in this case.\n\n\nHere's a sample Batch Response with 1 _successful_ and 1 _failed_ result:\n\n\n```json\n{\n    \"summary\": {\n        \"successfulRequests\": 1,\n        \"totalRequests\": 2\n    },\n    \"batchItems\": [\n        {\n            \"statusCode\": 200,\n            \"response\": {\n                \"routes\": [\n                    {\n                        \"summary\": {\n                            \"lengthInMeters\": 1758,\n                            \"travelTimeInSeconds\": 387,\n                            \"trafficDelayInSeconds\": 0,\n                            \"departureTime\": \"2018-07-17T00:49:56+00:00\",\n                            \"arrivalTime\": \"2018-07-17T00:56:22+00:00\"\n                        },\n                        \"legs\": [\n                            {\n                                \"summary\": {\n                                    \"lengthInMeters\": 1758,\n                                    \"travelTimeInSeconds\": 387,\n                                    \"trafficDelayInSeconds\": 0,\n                                    \"departureTime\": \"2018-07-17T00:49:56+00:00\",\n                                    \"arrivalTime\": \"2018-07-17T00:56:22+00:00\"\n                                },\n                                \"points\": [\n                                    {\n                                        \"latitude\": 47.62094,\n                                        \"longitude\": -122.34892\n                                    },\n                                    {\n                                        \"latitude\": 47.62094,\n                                        \"longitude\": -122.3485\n                                    },\n                                    {\n                                        \"latitude\": 47.62095,\n                                        \"longitude\": -122.3476\n                                    }\n                                ]\n                            }\n                        ],\n                        \"sections\": [\n                            {\n                                \"startPointIndex\": 0,\n                                \"endPointIndex\": 40,\n                                \"sectionType\": \"TRAVEL_MODE\",\n                                \"travelMode\": \"bicycle\"\n                            }\n                        ]\n                    }\n                ]\n            }\n        },\n        {\n            \"statusCode\": 400,\n            \"response\":\n            {\n                \"error\":\n                {\n                    \"code\": \"400 BadRequest\",\n                    \"message\": \"Bad request: one or more parameters were incorrectly specified or are mutually exclusive.\"\n                }\n            }\n        }\n    ]\n}\n```"
  }
}

⚼ Request

GET:  /route/directions/batch/{format}
{
x-ms-client-id:
{
Description: Specifies which account is intended for usage in conjunction with the Microsoft Entra ID security model. It represents a unique ID for the Azure Maps account and can be retrieved from the Azure Maps management plane Account API. To use Microsoft Entra ID security in Azure Maps see the following [articles](https://aka.ms/amauthdetails) for guidance. ,
Required: False ,
}
string ,
api-version:
{
Description: Version number of Azure Maps API. ,
Required: True ,
}
string ,
format:
{
Description: Batch id for querying the operation. ,
Required: True ,
}
string ,
}

⚐ Response (200)

{
batchItems:
{
Description: Array containing the batch results. ,
Required: False ,
}
[
{
response:
{
Description: The result of the query. RouteDirections if the query completed successfully, ErrorResponse otherwise. ,
Required: False ,
}
object ,
}
,
]
,
}

⚐ Response (202)

{
location:
{
Description: New URL to check for the results of the long-running operation. ,
}
string ,
}

⚐ Response (default)

{
error:
{
Description: The error object. ,
Required: False ,
}
{
code:
{
Description: The error code. ,
Required: False ,
}
string ,
message:
{
Description: The error message. ,
Required: False ,
}
string ,
target:
{
Description: The error target. ,
Required: False ,
}
string ,
details:
{
Description: The error details. ,
Required: False ,
}
[
{
code:
{
Description: The error code. ,
Required: False ,
}
string ,
message:
{
Description: The error message. ,
Required: False ,
}
string ,
target:
{
Description: The error target. ,
Required: False ,
}
string ,
details:
{
Description: The error details. ,
Required: False ,
}
[
string ,
]
,
additionalInfo:
{
Description: The error additional info. ,
Required: False ,
}
[
{
type:
{
Description: The additional info type. ,
Required: False ,
}
string ,
info:
{
Description: The additional info. ,
Required: False ,
}
object ,
}
,
]
,
}
,
]
,
additionalInfo:
{
Description: The error additional info. ,
Required: False ,
}
[
{
type:
{
Description: The additional info type. ,
Required: False ,
}
string ,
info:
{
Description: The additional info. ,
Required: False ,
}
object ,
}
,
]
,
}
,
}
Route_PostRouteDirectionsBatchSync (updated)
Description :  > [!NOTE] > > **Azure Maps Route v1 service retirement** > > The Azure Maps [Route v1](/rest/api/maps/route?view=rest-maps-1.0) service is now deprecated and will be retired on 3/31/28. To avoid service disruptions, all calls to Route v1 service will need to be updated to use [Route v2025-01-01](/rest/api/maps/route) service by 3/31/28. For more information, see [Migrate Azure Maps Route 1.0 APIs](/azure/azure-maps/migrate-route-v1-api). The `Post Route Directions Batch Sync` API is an HTTP `POST` request that sends batches of queries to the [Get Route Directions](/rest/api/maps/route/get-route-directions) API using a single synchronous request. You can call `Route Directions Batch` API to run either asynchronously (async) or synchronously (sync). The async API allows caller to batch up to **700** queries and sync API up to **100** queries. To call the `Post Route Directions Batch` API in a asynchronous request, see [Post Route Directions Batch](/rest/api/maps/route/post-route-directions-batch). ### Submit Synchronous Batch Request The Synchronous API is recommended for lightweight batch requests. When the service receives a request, it will respond as soon as the batch items are calculated and there will be no possibility to retrieve the results later. The Synchronous API will return a timeout error (a 408 response) if the request takes longer than 60 seconds. The number of batch items is limited to **100** for this API. ``` POST https://atlas.microsoft.com/route/directions/batch/sync/json?api-version=1.0&subscription-key={subscription-key} ``` ### Batch Response Model The returned data content is similar for async and sync requests. When downloading the results of an async batch request, if the batch has finished processing, the response body contains the batch response. This batch response contains a `summary` component that indicates the `totalRequests` that were part of the original batch request and `successfulRequests`i.e. queries which were executed successfully. The batch response also includes a `batchItems` array which contains a response for each and every query in the batch request. The `batchItems` will contain the results in the exact same order the original queries were sent in the batch request. Each item in `batchItems` contains `statusCode` and `response` fields. Each `response` in `batchItems` is of one of the following types: - [`RouteDirections`](https://docs.microsoft.com/rest/api/maps/route/getroutedirections#routedirections) - If the query completed successfully. - `Error` - If the query failed. The response will contain a `code` and a `message` in this case. Here's a sample Batch Response with 1 _successful_ and 1 _failed_ result: ```json { "summary": { "successfulRequests": 1, "totalRequests": 2 }, "batchItems": [ { "statusCode": 200, "response": { "routes": [ { "summary": { "lengthInMeters": 1758, "travelTimeInSeconds": 387, "trafficDelayInSeconds": 0, "departureTime": "2018-07-17T00:49:56+00:00", "arrivalTime": "2018-07-17T00:56:22+00:00" }, "legs": [ { "summary": { "lengthInMeters": 1758, "travelTimeInSeconds": 387, "trafficDelayInSeconds": 0, "departureTime": "2018-07-17T00:49:56+00:00", "arrivalTime": "2018-07-17T00:56:22+00:00" }, "points": [ { "latitude": 47.62094, "longitude": -122.34892 }, { "latitude": 47.62094, "longitude": -122.3485 }, { "latitude": 47.62095, "longitude": -122.3476 } ] } ], "sections": [ { "startPointIndex": 0, "endPointIndex": 40, "sectionType": "TRAVEL_MODE", "travelMode": "bicycle" } ] } ] } }, { "statusCode": 400, "response": { "error": { "code": "400 BadRequest", "message": "Bad request: one or more parameters were incorrectly specified or are mutually exclusive." } } } ] } ```
Reference :  Link ¶

⚶ Changes

{
  "#id": "Route_PostRouteDirectionsBatchSync",
  "Description": {
    "new": "\n\n> [!NOTE]\n>\n> **Azure Maps Route v1 service retirement**\n>\n> The Azure Maps [Route v1](/rest/api/maps/route?view=rest-maps-1.0) service is now deprecated and will be retired on 3/31/28. To avoid service disruptions, all calls to Route v1 service will need to be updated to use [Route v2025-01-01](/rest/api/maps/route) service by 3/31/28. For more information, see [Migrate Azure Maps Route 1.0 APIs](/azure/azure-maps/migrate-route-v1-api).\n\nThe `Post Route Directions Batch Sync` API is an HTTP `POST` request that sends batches of queries to the [Get Route Directions](/rest/api/maps/route/get-route-directions) API using a single synchronous request. You can call `Route Directions Batch` API to run either asynchronously (async) or synchronously (sync). The async API allows caller to batch up to **700** queries and sync API up to **100** queries. To call the `Post Route Directions Batch` API in a asynchronous request, see [Post Route Directions Batch](/rest/api/maps/route/post-route-directions-batch).\n### Submit Synchronous Batch Request\nThe Synchronous API is recommended for lightweight batch requests. When the service receives a request, it will respond as soon as the batch items are calculated and there will be no possibility to retrieve the results later. The Synchronous API will return a timeout error (a 408 response) if the request takes longer than 60 seconds. The number of batch items is limited to **100** for this API.\n```\nPOST https://atlas.microsoft.com/route/directions/batch/sync/json?api-version=1.0&subscription-key={subscription-key}\n```\n### Batch Response Model\nThe returned data content is similar for async and sync requests. When downloading the results of an async batch request, if the batch has finished processing, the response body contains the batch response. This batch response contains a `summary` component that indicates the `totalRequests` that were part of the original batch request and `successfulRequests`i.e. queries which were executed successfully. The batch response also includes a `batchItems` array which contains a response for each and every query in the batch request. The `batchItems` will contain the results in the exact same order the original queries were sent in the batch request. Each item in `batchItems` contains `statusCode` and `response` fields. Each `response` in `batchItems` is of one of the following types:\n\n  - [`RouteDirections`](https://docs.microsoft.com/rest/api/maps/route/getroutedirections#routedirections) - If the query completed successfully.\n\n  - `Error` - If the query failed. The response will contain a `code` and a `message` in this case.\n\n\nHere's a sample Batch Response with 1 _successful_ and 1 _failed_ result:\n\n\n```json\n{\n    \"summary\": {\n        \"successfulRequests\": 1,\n        \"totalRequests\": 2\n    },\n    \"batchItems\": [\n        {\n            \"statusCode\": 200,\n            \"response\": {\n                \"routes\": [\n                    {\n                        \"summary\": {\n                            \"lengthInMeters\": 1758,\n                            \"travelTimeInSeconds\": 387,\n                            \"trafficDelayInSeconds\": 0,\n                            \"departureTime\": \"2018-07-17T00:49:56+00:00\",\n                            \"arrivalTime\": \"2018-07-17T00:56:22+00:00\"\n                        },\n                        \"legs\": [\n                            {\n                                \"summary\": {\n                                    \"lengthInMeters\": 1758,\n                                    \"travelTimeInSeconds\": 387,\n                                    \"trafficDelayInSeconds\": 0,\n                                    \"departureTime\": \"2018-07-17T00:49:56+00:00\",\n                                    \"arrivalTime\": \"2018-07-17T00:56:22+00:00\"\n                                },\n                                \"points\": [\n                                    {\n                                        \"latitude\": 47.62094,\n                                        \"longitude\": -122.34892\n                                    },\n                                    {\n                                        \"latitude\": 47.62094,\n                                        \"longitude\": -122.3485\n                                    },\n                                    {\n                                        \"latitude\": 47.62095,\n                                        \"longitude\": -122.3476\n                                    }\n                                ]\n                            }\n                        ],\n                        \"sections\": [\n                            {\n                                \"startPointIndex\": 0,\n                                \"endPointIndex\": 40,\n                                \"sectionType\": \"TRAVEL_MODE\",\n                                \"travelMode\": \"bicycle\"\n                            }\n                        ]\n                    }\n                ]\n            }\n        },\n        {\n            \"statusCode\": 400,\n            \"response\":\n            {\n                \"error\":\n                {\n                    \"code\": \"400 BadRequest\",\n                    \"message\": \"Bad request: one or more parameters were incorrectly specified or are mutually exclusive.\"\n                }\n            }\n        }\n    ]\n}\n```",
    "old": "\n\nThe `Post Route Directions Batch Sync` API is an HTTP `POST` request that sends batches of queries to the [Get Route Directions](/rest/api/maps/route/get-route-directions) API using a single synchronous request. You can call `Route Directions Batch` API to run either asynchronously (async) or synchronously (sync). The async API allows caller to batch up to **700** queries and sync API up to **100** queries. To call the `Post Route Directions Batch` API in a asynchronous request, see [Post Route Directions Batch](/rest/api/maps/route/post-route-directions-batch).\n### Submit Synchronous Batch Request\nThe Synchronous API is recommended for lightweight batch requests. When the service receives a request, it will respond as soon as the batch items are calculated and there will be no possibility to retrieve the results later. The Synchronous API will return a timeout error (a 408 response) if the request takes longer than 60 seconds. The number of batch items is limited to **100** for this API.\n```\nPOST https://atlas.microsoft.com/route/directions/batch/sync/json?api-version=1.0&subscription-key={subscription-key}\n```\n### Batch Response Model\nThe returned data content is similar for async and sync requests. When downloading the results of an async batch request, if the batch has finished processing, the response body contains the batch response. This batch response contains a `summary` component that indicates the `totalRequests` that were part of the original batch request and `successfulRequests`i.e. queries which were executed successfully. The batch response also includes a `batchItems` array which contains a response for each and every query in the batch request. The `batchItems` will contain the results in the exact same order the original queries were sent in the batch request. Each item in `batchItems` contains `statusCode` and `response` fields. Each `response` in `batchItems` is of one of the following types:\n\n  - [`RouteDirections`](https://docs.microsoft.com/rest/api/maps/route/getroutedirections#routedirections) - If the query completed successfully.\n\n  - `Error` - If the query failed. The response will contain a `code` and a `message` in this case.\n\n\nHere's a sample Batch Response with 1 _successful_ and 1 _failed_ result:\n\n\n```json\n{\n    \"summary\": {\n        \"successfulRequests\": 1,\n        \"totalRequests\": 2\n    },\n    \"batchItems\": [\n        {\n            \"statusCode\": 200,\n            \"response\": {\n                \"routes\": [\n                    {\n                        \"summary\": {\n                            \"lengthInMeters\": 1758,\n                            \"travelTimeInSeconds\": 387,\n                            \"trafficDelayInSeconds\": 0,\n                            \"departureTime\": \"2018-07-17T00:49:56+00:00\",\n                            \"arrivalTime\": \"2018-07-17T00:56:22+00:00\"\n                        },\n                        \"legs\": [\n                            {\n                                \"summary\": {\n                                    \"lengthInMeters\": 1758,\n                                    \"travelTimeInSeconds\": 387,\n                                    \"trafficDelayInSeconds\": 0,\n                                    \"departureTime\": \"2018-07-17T00:49:56+00:00\",\n                                    \"arrivalTime\": \"2018-07-17T00:56:22+00:00\"\n                                },\n                                \"points\": [\n                                    {\n                                        \"latitude\": 47.62094,\n                                        \"longitude\": -122.34892\n                                    },\n                                    {\n                                        \"latitude\": 47.62094,\n                                        \"longitude\": -122.3485\n                                    },\n                                    {\n                                        \"latitude\": 47.62095,\n                                        \"longitude\": -122.3476\n                                    }\n                                ]\n                            }\n                        ],\n                        \"sections\": [\n                            {\n                                \"startPointIndex\": 0,\n                                \"endPointIndex\": 40,\n                                \"sectionType\": \"TRAVEL_MODE\",\n                                \"travelMode\": \"bicycle\"\n                            }\n                        ]\n                    }\n                ]\n            }\n        },\n        {\n            \"statusCode\": 400,\n            \"response\":\n            {\n                \"error\":\n                {\n                    \"code\": \"400 BadRequest\",\n                    \"message\": \"Bad request: one or more parameters were incorrectly specified or are mutually exclusive.\"\n                }\n            }\n        }\n    ]\n}\n```"
  }
}

⚼ Request

POST:  /route/directions/batch/sync/{format}
{
x-ms-client-id:
{
Description: Specifies which account is intended for usage in conjunction with the Microsoft Entra ID security model. It represents a unique ID for the Azure Maps account and can be retrieved from the Azure Maps management plane Account API. To use Microsoft Entra ID security in Azure Maps see the following [articles](https://aka.ms/amauthdetails) for guidance. ,
Required: False ,
}
string ,
api-version:
{
Description: Version number of Azure Maps API. ,
Required: True ,
}
string ,
format:
{
Description: Desired format of the response. Only `json` format is supported. ,
Required: True ,
}
string ,
routeDirectionsBatchQueries:
{
Description: The list of route directions queries/requests to process. The list can contain a max of 700 queries for async and 100 queries for sync version and must contain at least 1 query. ,
Required: True ,
}
{
batchItems:
{
Description: The list of queries to process. ,
Required: False ,
}
[
{
query:
{
Description: This parameter contains a query string used to perform an unstructured geocoding operation. The query string will be passed verbatim to the search API for processing. ,
Required: False ,
}
string ,
}
,
]
,
}
,
}

⚐ Response (200)

{
batchItems:
{
Description: Array containing the batch results. ,
Required: False ,
}
[
{
response:
{
Description: The result of the query. RouteDirections if the query completed successfully, ErrorResponse otherwise. ,
Required: False ,
}
object ,
}
,
]
,
}

⚐ Response (408)

{
error:
{
Description: The error object. ,
Required: False ,
}
{
code:
{
Description: The error code. ,
Required: False ,
}
string ,
message:
{
Description: The error message. ,
Required: False ,
}
string ,
target:
{
Description: The error target. ,
Required: False ,
}
string ,
details:
{
Description: The error details. ,
Required: False ,
}
[
{
code:
{
Description: The error code. ,
Required: False ,
}
string ,
message:
{
Description: The error message. ,
Required: False ,
}
string ,
target:
{
Description: The error target. ,
Required: False ,
}
string ,
details:
{
Description: The error details. ,
Required: False ,
}
[
string ,
]
,
additionalInfo:
{
Description: The error additional info. ,
Required: False ,
}
[
{
type:
{
Description: The additional info type. ,
Required: False ,
}
string ,
info:
{
Description: The additional info. ,
Required: False ,
}
object ,
}
,
]
,
}
,
]
,
additionalInfo:
{
Description: The error additional info. ,
Required: False ,
}
[
{
type:
{
Description: The additional info type. ,
Required: False ,
}
string ,
info:
{
Description: The additional info. ,
Required: False ,
}
object ,
}
,
]
,
}
,
}

⚐ Response (default)

{
error:
{
Description: The error object. ,
Required: False ,
}
{
code:
{
Description: The error code. ,
Required: False ,
}
string ,
message:
{
Description: The error message. ,
Required: False ,
}
string ,
target:
{
Description: The error target. ,
Required: False ,
}
string ,
details:
{
Description: The error details. ,
Required: False ,
}
[
{
code:
{
Description: The error code. ,
Required: False ,
}
string ,
message:
{
Description: The error message. ,
Required: False ,
}
string ,
target:
{
Description: The error target. ,
Required: False ,
}
string ,
details:
{
Description: The error details. ,
Required: False ,
}
[
string ,
]
,
additionalInfo:
{
Description: The error additional info. ,
Required: False ,
}
[
{
type:
{
Description: The additional info type. ,
Required: False ,
}
string ,
info:
{
Description: The additional info. ,
Required: False ,
}
object ,
}
,
]
,
}
,
]
,
additionalInfo:
{
Description: The error additional info. ,
Required: False ,
}
[
{
type:
{
Description: The additional info type. ,
Required: False ,
}
string ,
info:
{
Description: The additional info. ,
Required: False ,
}
object ,
}
,
]
,
}
,
}